If you have a company A that has a journal set up with bank synchronization, and a company B that is a branch of company A, you have access to the journal and the bank synchronization (account.online.link) of company A in company B.

This causes an issue when fetching the transactions from the context of company B, as that will create the fetched transactions with a `company_id` set to B, which will cascade on the journal entries and items linked to these transactions.

To ensure the correct company is set on the transactions, we force the company in the context when creating them.

As a result:
- When only company A is selected, transactions are correctly created in company A.
- When both company are selected, no matter if the transactions are fetched from A or B, the transactions are correctly created in company A.
- When only company B is selected, the user is faced with an access error, as Odoo is trying to open a view with the fecthed transaction, which belong to company A.

To prevent this access error, it was decided that the "Fetch Transaction" buttons should not appear when the company owning the bank synchronization is not selected.

A new computed field was then introduced on the account.online.account to check if we should allow fetching given the currenctly selected companies. That field is also added on the account.online.link as a logical conjunction of its account.online.account values of the field.

These fields are then used to decide whether if we show the transaction fetching buttons on the dashboard and on the online link form view.

Another issue with branches is the 'connect bank' button.

With the same configuration as above, let's have companies A and B enabled, with B as the selected company.

If you connect a bank to a journal belonging to company A by clicking on the 'connect bank' button on the dashboard, it will successfully connect, but the account.online.link will belong to company B.
Then, if you try to access the accounting dashboard with only company A enabled, you will be faced with an access error, as the journal from company A tries to diplay informations computed with the above account.online.link of company B.

To prevent this, we only make the 'connect bank' button appear if company A (i.e. the company owning the journal) is selected as the active company.

This did not require a new field, and was done by adding an entry in the dashboard data.

opw-4515862

Forward-Port-Of: odoo/enterprise#84694
Forward-Port-Of: odoo/enterprise#83134

### Issue:
If `l10n_br_avatax` is installed, portal users are not able to view any products via the shop on a Website. An inherited field's domain requires access to the `city_id` from the Website's company's `res.partner` record, but Portal users cannot access this.

This is only an issue on 18.2+, as this value was originally stored in the field cache due to a separate workflow in previous versions. Previously, opening a product would trigger `_compute_fiscal_position_id`, which would eventually call `_compute_address`. `_compute_address` contains a sudo, allowing the retrieval of the address fields (like `city_id`) and would store them in cache. The domain would be able to retrieve from the cache rather than needing to fetch the values.

In 18.2, the `fiscal_position` workflow was refactored, and the address fields are no longer stored in cache for the domain `_l10n_br_property_service_code_origin_id_domain` to access prior to hitting any security limits.

### Solution:
We should be safe to `sudo` the `city_id`, allowing the domain to complete.

opw-4732256

Forward-Port-Of: odoo/enterprise#84140

A `CheckViolation` traceback occurs when uploading an XML file that lacks the `Nombre` attribute.

**Steps to Reproduce:**
- Install `l10n_mx_edi` module
- Navigate to `Accounting>Vendors>bills` try to upload [this](https://drive.google.com/file/d/1DRON2ftkDhwASqy_OFi9FtUNj7tODyKm/view?usp=sharing) `[demo file]`

**Error:**
`CheckViolation: new row for relation 'res_partner' violates check constraint 'res_partner_check_name'`

**Root Cause:**
- The `Nombre` attribute in the XML file is missing, which results in the `name` field being set to `None` at [1] in the `partner_vals` dictionary. 
[1]-
https://github.com/odoo/enterprise/blob/1d06bf93a2be03e969a5fce134b7323a70b2aef1/l10n_mx_edi/models/account_move.py#L2504
- The `res.partner` model has a database constraint (**res_partner_check_name**) that requires the `name` field to be non-null. When attempting to create a `partner` with a None value for `name`, the database raises a **CheckViolation error**.

**Solution:**
- Added a check in the `_l10n_mx_edi_import_cfdi_fill_partner` method to handle cases where the `Nombre` attribute is missing.
- This prevents the creation of a partner with an invalid `name` field and avoids the **CheckViolation error**.

sentry- 6546905710

Forward-Port-Of: odoo/enterprise#83776