Currently, adding a chatter in a form view using web studio causes an error when the model does not inherit from mail.thread model.

**Steps to Reproduce:**
1. Install the `data_cleaning` and `web_studio` modules.
2. Data Cleaning > Configuration > Field Cleaning (form view).
3. Activate studio and open the XML view from the "View" tab.
4. Add `<chatter/>` tag inside the `<form>` tag and try to save the view.

**Error:**
`AttributeError - 'data_cleaning.model' object has no attribute '_get_thread_with_access'`

**Cause:**
The `.../mail/thread/data` controller passes the current model as a `thread_model` but the chatter can only be added module that inherits the 'mail.thread' module. When a chatter is added to a form view of a model that does not inherit mail.thread, resulting in an AttributeError. - [1]

**Fix:**
This commit prevents adding chatter to form views of models that do not support it. Instead of a traceback, a validation error is shown to the user.

[1]: https://github.com/odoo/odoo/blob/71e86f38c7699aaea980c929c67835a3495edf55/addons/mail/controllers/thread.py#L18

sentry-6792833694

4d844b7f3b570d7c3d978c6f10c351c48553df0b was a backport that was developed when demo data was installed during CI.

However, time has passed, and demo isn't installed anymore causing the following:

```python
Traceback (most recent call last):
  File "/data/build/enterprise/sale_amazon/tests/test_amazon.py", line 541, in test_sync_orders_replacement
    "partner_id": self.env.ref("base.res_partner_1").id,
  File "/data/build/odoo/odoo/api.py", line 596, in ref
    res_model, res_id = self['ir.model.data']._xmlid_to_res_model_res_id(
  File "/data/build/odoo/odoo/addons/base/models/ir_model.py", line 2215, in _xmlid_to_res_model_res_id
    return self._xmlid_lookup(xmlid)
  File "<decorator-gen-43>", line 2, in _xmlid_lookup
  File "/data/build/odoo/odoo/tools/cache.py", line 104, in lookup
    value = d[key] = self.method(*args, **kwargs)
  File "/data/build/odoo/odoo/addons/base/models/ir_model.py", line 2208, in _xmlid_lookup
    raise ValueError('External ID not found in the system: %s' % xmlid)
ValueError: External ID not found in the system: base.res_partner_1
```

This commit creates a new partner on the fly instead.

runbot-241943

Forward-Port-Of: odoo/enterprise#112131

Since its introduction (https://github.com/odoo/odoo/pull/76734), the "mail.catchall.domain.allowed" system parameter is normally sanitized by `_sanitize_allowed_domains` when using `set_param`.

But the method is not run when the system parameter is created manually, for example through the UI, because the current conditional logic is not triggered for write and create call.

This can be an issue if for example the use submits this value: "domain1.com, domain2.com,domain3.com"

The comma seperated list will only be split by ',', meaning that the second element is " domain2.com" (space character in front). As such, that domain will not be used as expected, since most flows using that data will end up comparing "domain2.com" vs " domain2.com", and not considering it a match.

Before this fix:
Create new record in System parameters with
key = "mail.catchall.domain.allowed"
value = "domain1.com, domain2.com,domain3.com"
-> after save, value == "domain1.com, domain2.com,domain3.com"

After this fix:
-> after save, value == "domain1.com,domain2.com,domain3.com"

OPW-5505414

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

Forward-Port-Of: odoo/odoo#244279

### Steps to reproduce
------------------
- Install `l10n_ae` module.
- Go to *Settings → Countries* and rename the country "United Arab Emirates" (e.g. change it to "UAE").
- Upgrade the `l10n_ae` module.

### Issue
-----
The file `l10n_ae/data/res.bank.csv` references the country using its name ("United Arab Emirates"). During the module upgrade, the CSV import tries to resolve the country relation using the country name. If the country name has been modified by the user (for example to "UAE"), the lookup fails and the module upgrade crashes with:

```python3
No matching record found for name 'United Arab Emirates' in field 'Country'
```

### Root Cause
----------
Using translatable/display names in CSV data is unreliable, as these values can be customized or translated by users.

### Fix
---
Replace the country name reference with the stable XMLID `base.ae` in `res.bank.csv`.

Using XMLIDs ensures consistent resolution regardless of name changes or translations.

opw-6015302
upg-3950261
tbg-2492

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

**Steps to reproduce:**
* Go to the Contacts app and create a new partner.
* In the VAT field, type a valid VAT number that includes the country code prefix (e.g., a Danish VAT like DK12345678).
* Trigger the autocomplete suggestion.

**Observed behavior:**
* The autocomplete by VAT does not return any results. It falls back to an autocomplete by name, which relies on the VAT string and also yields no results.

**Cause:**
* The `jsvat` frontend library requires the VAT string to include the country code prefix (e.g. DK12345678) to evaluate it correctly as a VAT number and trigger the VAT autocomplete flow.
* However, the backend IAP `search_by_vat` API expects the VAT number without the country prefix in the `query` field, as the country code is provided as a separate `query_country_code` parameter. Passing the full VAT string prevents the IAP service from finding matches.

**Fix:**
* Modified `autocomplete_by_vat` in `res_partner.py` to strip the `query_country_code` prefix from the `vat` string before passing it to the IAP API `search_by_vat`.
* The full, unmodified VAT string is still preserved for the `check_vies` fallback, as VIES requires the full country code prefix.

opw-5974250