Original PR description

The portal task list searched titles with
['|', ('name', 'ilike', search), ('id', 'ilike', search)]. Applying ilike to the integer id casts it to text, which no index can serve, and OR-ing that branch with the title prevents the trigram index on name from being used at all, so every search fell back to a full scan of project_task. The id branch is now added only when the term is numeric, as an equality on the primary key, keeping the title lookup on its trigram index.

Benchmark on 200k tasks, PostgreSQL EXPLAIN ANALYZE, selective term matching 5 rows, median of 3 runs:

  before   Parallel Seq Scan on project_task    ~150 ms
  after    Bitmap Index Scan (name gin_trgm_ops)  ~0.5 ms

opw-5478903

Original PR description

**Steps to reproduce:**
  * Set up a French company and configure Peppol E-invoicing.
  * Install `account_edi_ubl_cii` module.
  * Create a company partner (customer) and set a **Reference** value on the company contact under 
     **Customer** -> **Settings** -> **Sales and Purchase**.
  * Create a child contact under that company and set a different Reference value.
  * Create an invoice using the child contact as the invoice partner and confirm the invoice.
  * Send it via Peppol.

**Observed Behaviour:**
  * The BuyerReference in the generated XML contains the reference of the parent
  (commercial partner) Instead of the child contact used on the invoice.

**Cause:**
  * The buyer reference was taken from the commercial partner instead of the
  invoice partner.

**Fix:**
  * Update the condition to use the invoice partner's reference when available;
  Otherwise, fall back on the commercial partner's reference.

opw - 6330649

Forward-Port-Of: odoo/odoo#273700

Original PR description

**Steps to reproduce:**

- Install module `l10n_fr_pdp` and configure French e-Invoicing.
- Create a customer has a valid SIREN/SIRET (company_registry) but no VAT number.
- Create an invoice for the customer and confirm the invoice.
- Check the available sending methods.

**Observed Behavior:**
The French E-Invoicing option is disabled because the customer is identified as a B2C partner when no VAT number is set.

**Cause**:
The B2C detection relies on the partner's VAT number instead of its SIREN/SIRET. As a result, French companies without a VAT number but with a valid SIREN are classified as B2C.

**Fix**:
Determine whether a partner is B2C based on the presence of a valid SIREN/SIRET (derived from `company_registry`) instead of the VAT number. This correctly identifies French business partners that are eligible for French e-Invoicing even when they do not have a VAT number configured.

opw-6357756

Forward-Port-Of: odoo/odoo#278060

Original PR description

When mass-editing the Analytic Distribution field on several records at
once, and creating a new distribution at once, will close the
creation dialog before the user could fill it in.

Steps to reproduce:
- Enable Analytic Accounting
- Open Accounting > Journal Items
- Enable the Analytic Distribution column
- Select 2 journal items and click on the Analytic Distribution
- Click on 'Update', fill a distribution, then click "New Model"
- Confirm the multi-edit update

Issue:
The create Analytic Distribution model dialog closes on its own instead
of staying open, so the model can never be saved.

Analysis:
After https://github.com/odoo/odoo/commit/12a61fa5ab7c56a42020c50c683df8ed52f1fb01, in multi-edit, save() ends reloading the list, unmounting
the AnalyticDistribution widget, that closes the model dialog it just opened.

opw-6405219

Forward-Port-Of: odoo/odoo#281141

Original PR description

**Issue**:
Sending a WhatsApp template with 10 or more variables can assign values to the wrong placeholders when the body contains mixed variable types, such as free text, field, or user name variables.
Templates containing only free-text variables are not affected.

**Reason**:
Meta consumes template parameters positionally, but for mixed variable types, Odoo built the parameter list using the template variable recordset order.
That order can differ from the numeric placeholder order, notably placing {{10}}, {{11}}, {{12}}... before {{1}}
when sending the message, as the payload parameters are not ordered by their numeric placeholder index.

**Fix:**
Sort body variables by their numeric placeholder index before preparing the Meta payload.

Task-6401501

Forward-Port-Of: odoo/enterprise#125671