### Commit 1: [FIX] account_peppol: Remove useless div
The div is replaced few lines below, so no need to make it
visible/invisible.

task-no

### Commit 2: [FIX] account_edi_ubl_cii: add belgian EAS translation
task-no

### Commit 3: [FIX] account_edi_ubl_cii: fix typo in EAS
task-no

### Commit 4: [FIX] account_peppol: clean calls to proxy
Before this commit, when calling our Peppol proxy, here is what the call
graph would look like (prefixed by the module the method belongs to):
`account_peppol._call_peppol_proxy`
-> `account_peppol._make_request`
--> `account_peppol._call_peppol_proxy`
---> `account_edi_proxy_client._make_request`

We simplify this to:
`account_peppol._call_peppol_proxy`
-> `account_edi_proxy_client._make_request`

task-no

### Commit 5: [FIX] account_peppol: fix reopening of Print & Send wizard
With previous commit [1], we broke the flow when registering to Peppol
coming from the Print & Send wizard. The Print & Send wizard was not
reopening after successful registration.

task-no

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)

Before this commit, emoji navbar simply had `.overflow-auto`. The size of emoji category depends on browser/OS for the style of emoji, but browsers also differ in the way they render font unicodes. This means that overflow never happens on some configuration, and in a few of them it always occur.

The size of emoji picker container is good and we want to keep it fixed, as it plays nicely with the rest of UI. For the size of emojis, as long as we rely on font unicode, we have to live with the different sizing.

This commit suggests a new way to manage overflow which doesn't show a scroll bar while letting browser/OS choose their way to render emojis: we detect whether emoji tabs overflow, and when so it fills as most emoji it can without overflow. Navbar has many "panels", and switching to panels happen either manually (click on >> and << buttons) or with scrolling of emoji picker without any search.

Commit also makes the following minor improvements:
- category section position sticky was not completely hiding emoji list below (e.g. on Chrome macOS). This is fixed with a `.align-self-stretch` on the section
- emoji categories are centered with emoji picker

Task-4413819

-------------

_(note: size of emoji in navbar is artificially bigger to simulate some rendering in few browser/OS that have always overflow)_
Before / After
![before](https://github.com/user-attachments/assets/12375001-2c2d-4bfb-90c9-d4189c799370) ![after](https://github.com/user-attachments/assets/0d5e07ff-2d18-4f0b-93a8-a8b9aefe68b1)

**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