Description
-----------
Following odoo/enterprise@88b8de95e1a28a8037a386fc8fb6a044a98217e7 and odoo/enterprise@777ebe3918aacdfe3f09078f542e2a784f72a67f, opening the Phone app for a salesperson is slow on databases with an already large volume of `voip.call` and `res.users`.

This is due to the disjonction (OR-ing) between `ir.rule` `voip_call_rule_user` and `voip_call_team_access_rule`. It leads to Postgres doing a naive O(n^2) join between all `voip.call` and the `res.users` to only then do some post-filtering.

Technically the domain introduced by `voip_call_rule_user` becomes redundant once `voip_call_team_access_rule` is applied for `read`, as reading your own sales team calls includes also your own calls. Sadly there is currently no way to drop the redundant condition only for salesperson, without relaxing the rule for all `Role / User`.

This commit addresses the issue by inlining the ids when resolving `_search_crm_team_ids` directly, to avoid the elaborate subquery generated when resolving the One2many `crm_team_member_ids`. We fall back on the previous behavior in case we might be injecting too many ids, which might introduce a performance regression. We assume that on average this won't be the case. This leads to trivial queries that properly use relevant indexes.

Benchmark
---------
On a database with over 10M `voip.call` and `res.users`, for a salesperson to open the Phone's app default list view with no default filter (the default setup), took:

| Before | After | Speed-up |
|--------|-------|----------|
| 14sec  | 150ms | 93x      |


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