The main goal is to rationalize the use of operators to simplify query generation and to make it possible to run optimizations to send a more efficient query to the database. Domain rewriting and optimization is separated from query generation which accepts a fixed set of operators.

The main new introduced operator is **any** (and its inverse **none**) which apply to relational fields: these are quantifiers which have as a value another domain that will be applied on the comodel.
It allows to specify domains which were not possible to express before:
- which res.partner has a confirmed order where the price > 1000
`[('sale_order_ids', 'any', [('state', '=', 'sale'), ('amount_total', '>', 1000)])]`
- which res.partner does not have a tag 'x'
`[('category_id, 'none', [('name', '=', 'x')])]`
- which res.partner have or don't have expired quotations

The internal representation of domains as polish-notation lists is handy for serializing them. The new implementation uses a Domain class to represent domains which is backwards-compabile with the polish notation. To build domains, there is a D() builder function and you can still use AND() and OR() or infix operators.
The Domain instances should be considered as immutable.

    list(D(some_domain)) # normalized some_domain
    D('a', '=', 1) | ~D('b', '=', 2) == D(['|', ('a', '=', 1), '!', ('b', '=', 2)])

New operators can be added, check the 'ref' operator for an example. The new API is used in some core modules to show can what is possible. At the same time, we have an `unaccent` implementation in python for filtered_domain.


---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Without `auto_join=True` a query the Trial Balance report has extra tables
scanning because of the following where condition:

```
      "account_move_line"."account_id" in (
        SELECT
          "account_account".id
        FROM
          "account_account"
        WHERE
          (
            "account_account"."user_type_id" in (
              SELECT
                "account_account_type".id
              FROM
                "account_account_type"
              WHERE
                (
                  "account_account_type"."include_initial_balance" IS NULL
                  or "account_account_type"."include_initial_balance" = false
                )
            )
          )
          AND (
            "account_account"."company_id" IS NULL
            OR (
              "account_account"."company_id" in (1)
            )
          )
      )
```

---

task-2743905

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Before there were where-condition that requires extra table scanning

```
                    ...
                    AND (
                        "account_aged_receivable"."account_id" in (
                            SELECT
                                "account_account".id
                            FROM
                                "account_account"
                            WHERE
                                (
                                    "account_account"."internal_type" = 'receivable'
                                )
                                AND (
                                    "account_account"."company_id" IS NULL
                                    OR (
                                        "account_account"."company_id" in (
                                            1
                                        )
                                    )
                                )
                        )
                    )
```

Benchmarks for a dummy DB with 1M account.move.line records:
total time for `get_report_informations` drops from 1500 ms to 150 ms

---

task-2737991