[12.x] Add WhereNotAny, WhereNotAll methods to Query Builder

[ezequidias]

This PR introduces new methods to the Query Builder and refactors existing ones to enhance consistency and clarity:

• whereNotAny: Adds a "where not" clause for multiple columns with "or" conditions between them.
• orWhereNotAny: Adds an "or where not" clause for multiple columns with "or" conditions between them.
• whereNotAll: Adds a "where not" clause for multiple columns with "and" conditions between them.
• orWhereNotAll: Adds an "or where not" clause for multiple columns with "and" conditions between them.

Additionally, the previously existing methods whereNone and orWhereNone have been refactored to serve as aliases for whereNotAny and orWhereNotAny, respectively. This change addresses concerns regarding the naming inconsistency and potential confusion associated with the whereNone method, as discussed in PR #52383.​

The whereNone method's naming did not align with Laravel's established conventions, leading to potential confusion among developers. By introducing whereNotAny and whereNotAll, we adhere to a more intuitive and consistent naming pattern, enhancing code readability and maintainability. This approach also aligns with the enhancements proposed in PR #52361, ensuring a comprehensive and logical set of query builder methods.

To maintain backward compatibility, whereNone and orWhereNone have been retained as aliases. However, it is recommended that these methods be deprecated in future Laravel releases to encourage developers to adopt the more appropriately named methods.

[taylorotwell]

Thanks for your pull request to Laravel!

Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.

If applicable, please consider releasing your code as a package so that the community can still take advantage of your contributions!