Before this commit, when opening message reaction menu in a chat window, clicking on ESC was closing the chat window.

Steps to reproduce:
- as Mitchell Admin, open a chat window of channel General from click on messaging menu in systray
- add an emoji reaction to the last message
- click on composer to have focus on it
- mouse hover the reaction then click on emoji reaction tooltip
- press ESC when the message reaction menu is open

=> it closes the chat window instead of message reaction menu.

This happens because when opening the message reaction menu, the dialog is mounted. It detects dropdown is closed after a delay, and when closing the dropdown it recovers the focus before the opening of dropdown, which could be the composer of chat window. In the case when the focus was on composer, pressing ESC on message reaction menu will close the chat window due to composer being focused.

This commit fixes the issue by immediately setting the dropdown state to close when clicking to open message reaction menu, so that it won't recover the old focused element such as the composer.

---------

This commit also fixes a related minor bug when closing the message reaction menu then hovering the reaction was not showing the dropdown/tooltip of reaction. This happens because the `useHover()` hook was not aware the click on dropdown content closes the hovered ref, thus it kept internally thinking the item is hovered so it wasn't updating UI to open dropdown or reaction.

This is fixed by adding a parameter `stateObserver` to help the `useHover()` hook to re-check whether the targets are present on UI. Thanks to this, it can detect whether the currently hovered target has been removed, thus invoking the behaviour to mark is as no longer hovered.

task-4351992

Before
![before](https://github.com/user-attachments/assets/de6c8dc2-6c96-4399-8ec0-81d81cbd2dd7)

After
![after](https://github.com/user-attachments/assets/26607676-1210-4e1e-9968-ab7274c83159)

**Issue:**
The client gets an error while accessing an employee's payslips if that employee has a contract based on attendances with a null allowed value for its working schedule.

**Expected:**
The client should be able to access the payslips regardless on the working schedule value, even blank.

**Steps to reproduce:**
- Activate Payroll app and presence based on attendances in employees' settings;
- Open or create a contract through an employee's file;
- Set "Work Entry Source" to "Attendances" and leave "Working Schedule" empty;
- Try to access the employee's payslips through the action button.

**Cause:**
No timezone found on a contract's calendar because the calendar is null. [https://github.com/odoo/enterprise/blob/18.0/hr_payroll/models/hr_payslip.py#L1141](https://github.com/odoo/enterprise/blob/18.0/hr_payroll/models/hr_payslip.py#L1141
)

**Fix:**
Add a default value on `'UTC'` if no calendar has been found.

**Linked:**
Community PR :
https://github.com/odoo/odoo/pull/186222

opw-4268672

This PR fixes an issues about the terms & conditions overlapping the rest of the content on the `website_sale` payment page.

Prior to this PR, the terms & conditions was positioned using a `position-absolute` with a `bottom-0`, resulting in the element extending to the topside if its content is very long. This led to some overlapping issues with the others elements of the view.

To prevent this issue to happen, we position the element with a `top-100` and remove the `<div>` that aimed to handle the spacing at the bottom. We now manage this spacing with a utility class.

opw-4373853

| 17.0 | This PR |
|--------|--------|
| <img width="472" alt="image" src="https://github.com/user-attachments/assets/6b4b768f-9764-45aa-84b8-94fcab059f30" /> | <img width="461" alt="image" src="https://github.com/user-attachments/assets/5cd8548e-9b8f-4036-84dd-3f224779af27" /> | 

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

Forward-Port-Of: odoo/odoo#191346

Currently when we validate a transfer with products tracked by serial number, we may run into a bottleneck when the `quality_mrp` module is installed. That's because there's 1 move_line by Serial Number and inside `_create_assign_production_lot` those move_lines are grouped by `(company_id, product_id, lot_name)`. As we are tracking by Serial Number, each of these group key will be unique. Also, the mls are grouped in key_to_mls using `__union__` which calls `browse` to produce a recordset, effectively setting the `_prefetch_ids` of the results to `_ids`. Therefore, in the sml `write` override in quality_mrp when there's a condition on `self.sudo().check_ids`, the `_prefetch_ids` of self will only be the id in self, leading to 1 SELECT query by SML, i.e. 1 SELECT query by serial number.

This wouldn't be that much of an issue if `quality_check.move_line_id` was properly indexed but that's not the case.

So this commit first adds a missing `btree_not_null` index on `quality_check.move_line_id` to change the query plan from Seq Scan to Index Scan. Then we manually set the `_prefetch_ids` in `_create_and_assign_production_lot` to reduce the number of queries.

#### speedup

In a 17 database with 750 000 quality checks, on hot cache, adding the index makes a single query go from ~50ms to 0.250ms.

When doing a transfer of 1000 serial numbers, setting the `_prefetch_ids` reduce the number of queries from 1000 to 1. This query takes around 120ms on hot cache without the index.

Both with the index and the `_prefetch_ids`, the total time of the `_create_and_assign_production_lot` method when validating a transer of 1000 serial numbers goes from 50ms * 1000 = 50s -> 2ms * 1 = 2ms.

opw-4285293

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

Forward-Port-Of: odoo/odoo#190479

Description of the issue/feature this PR addresses:
- In Mexico, failing to assign an appropriate account for cash basis movements can be considered illegal. Therefore, it's essential to set a default one for Mexican companies.

Current behavior before PR:
- When the 'Cash Basis' (`tax_exigibility`) setting is enabled (via Settings → Accounting → Taxes), no 'Base Tax Received Account' (`account_cash_basis_base_account_id`) is set by default for companies using the 'Mexico' fiscal localization.

Desired behavior after PR is merged:
- For companies with Mexican fiscal localization, set the default *Base Tax Received Account* to the account with code `899.01.99`. This account, already defined in the [l10n_mx data](https://github.com/odoo/odoo/blob/17.0/addons/l10n_mx/data/template/account.account-mx.csv#L47), is specified by the SAT (_Servicio de Administración Tributaria_, Mexico's primary tax authority) for miscellaneous or generic adjustments (see their [official documentation](http://omawww.sat.gob.mx/fichas_tematicas/buzon_tributario/Documents/codigo_agrupador.pdf#page=22)).

opw-[4393526](https://www.odoo.com/odoo/project.task/4393526)

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

Forward-Port-Of: odoo/odoo#190279

Currently, an error occurs when validating stock moves without location.

Step to produce:

- Install the `mrp_subcontracting` module (make a debugger on).
- Create a product, add some quantities, and remove the value of 'Production Location' and 'Inventory Location' from it.
- Click on the 'Bills of Materials' button which is in the breadcrumbs of the product form view to create a bom of this product, And set a 'BoM Type' as Subcontracting and add an Administrator as 'Subcontractors'.
- Go to Inventory / Operations / Transfers / Receipts and create a new 'Receipts', add an Administrator as 'Receive From', and add product in 'Operations' which we created bom.
- Open a form view of 'Receive From' (res.partner) and remove value from 'Subcontractor Location' filed which is in the 'Sales & Purchase' tab.
- Again come to receipts form view and try to validate it.

`ValueError: Expected singleton: stock.location()`

This occurs because the system attempts to get 'location_id' from the stock move at [1], but it is not available.

Link [1]: https://github.com/odoo/odoo/blob/231952114ae730bb8d4671f4a61f738e8b6dd5b8/addons/stock/models/stock_move.py#L1566

To resolve this issue, add a condition to check if location_id is not available then use the company's subcontracting location as the default value.

Sentry-6156032937

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

Forward-Port-Of: odoo/odoo#191005

**Issue:**
When the currency symbol display position is set to `After Amount`, the currency sign of a negative amount (credit) in a bank journal entry overlaps with the amount.
![Capture d’écran 2024-12-12 à 15 40 19](https://github.com/user-attachments/assets/9c7f5773-9962-4d4a-8df8-de2680981c69)

**Expected:**
The `Amount` field should consistently display the currency symbol after the amount when configured as such, even for negative values.

**Steps to reproduce:**
1. Activate the Accounting app.
2. Go to `Accounting / Configuration / Accounting / Currencies`.
3. Select the company's currency and enable debug mode.
4. Set the `Display` `Symbol Position` to `After Amount` and save.
![Capture d’écran 2024-12-12 à 15 40 39](https://github.com/user-attachments/assets/bfc0b12f-8042-4408-94ea-e7c7a66da858)
5. Navigate to `Accounting / Dashboard` and open the `Bank` journal.
6. Locate an entry with a credit (negative) value.

**Cause:**
The negative sign (`-`) is correctly displayed before the input field, but it is not added to the "ghost field" used for layout alignment, causing the currency symbol to overlap with the amount.

**Fix:**
Ensure the negative sign is included before the ghost field as well, aligning the visual layout with the actual value.
![Capture d’écran 2024-12-12 à 15 39 57](https://github.com/user-attachments/assets/dce5b9ae-0f38-4ba2-b041-1a24fb549074)


opw-4348298

Forward-Port-Of: odoo/enterprise#75567

When fetching the Routing in project->task, the map view shows the error "To get routing on your map, you first need to set up your Mapbox token. -> Set up token" even if they already have the token set up.

This happens when, for example:
 if you have 3 tasks where 2 of them have the customer field
filled and one doesn't. The function _fetchRoute tried to filter out the records that don't have the latitude/longitude. But, here, since one of the records doesn't have a partner, when it's trying to look into partner.partner_latitude, it throws an error. After the error, mapBoxToken is set to '' in _partnerFetching, and called _openStreetMapAPI() resulting in displaying the error, "to get routing on your map, you first need to set up your Mapbox token."

So, adding record.partner in the filter will help filter out the records that don't have partner.

To Reproduce on Runbot:
1. Set up Mapbox token
2. Go to Project->Task
3. Create 3 Tasks ( 2 with customer and 1 without customer )
4. Go to the map view and it'll display the error.

opw-3682829

Forward-Port-Of: odoo/enterprise#73238
Forward-Port-Of: odoo/enterprise#55580

**Issue:**
Some terms don't appear in Spanish in DIAN invoice PDF files.
![image](https://github.com/user-attachments/assets/3a76f66c-9a53-473c-a5cd-68ef1e4c3980)

**Expected:**
These terms should be translated in Spanish.

**Steps to reproduce:**
- Activate Accounting app in a Colombian database;
- Configure the DIAN credentials, client, journal and product (https://www.odoo.com/documentation/18.0/applications/finance/fiscal_localizations/colombia.html?highlight=dian);
- Create a customer invoice;
- Send and print with (only) DIAN checkbox checked;
- Open the PDF for the invoice.

**Cause:**
No translations (or erroneous ones) have been found for these keys.

**Fix:**
Add Spanish translations for these terms.
<img width="642" alt="Capture d’écran 2024-12-09 à 11 52 44" src="https://github.com/user-attachments/assets/77f548f4-f87e-4823-9fdc-5b54d0db2a1f">
Backport of Odoo 18 fix: https://github.com/odoo/enterprise/commit/99f332e3211cf17eb7bf0a970544dd0e0e07a9f8

**Testing:**
Testing needs actual credentials and complete configuration (including setting the client's language to LATAM Spanish)
![Capture d’écran 2024-12-09 à 11 34 54](https://github.com/user-attachments/assets/3bbea0c4-2696-4fb9-88d0-38be9a8cae06)


opw-4343184

Forward-Port-Of: odoo/enterprise#75913