This update adds a new test to ensure the structure of payment data sent to our payment processor (Odoofin) remains consistent. This helps prevent unexpected changes on Odoofin's side and ensures developers are aware of any necessary updates there. It's a proactive measure to maintain reliable payment processing.

Add a test asserting the payment payload structure sent to Odoofin.

The goal is to safeguard against unintended payload changes that are not
handled on Odoofin's side by making such changes explicit during testing,
and reminding developers that corresponding updates may also be required
there.

No task ID

Forward-Port-Of: odoo/enterprise#118182
Forward-Port-Of: odoo/enterprise#117260

This update corrects a translation issue within the Odoo Enterprise Gantt view. The button used to toggle display modes was not properly translated, preventing users from seeing the view in their preferred language. This fix ensures all users can consistently access and utilize the Gantt view in their local language.

The title of the button allowing to toggle the display mode in the Gantt view was not translated. This commit adds a getter to compute the title based on the current display mode, and uses it in the template.

Issue reported by translator.

Forward-Port-Of: odoo/enterprise#118173
Forward-Port-Of: odoo/enterprise#117739

This update removes a redundant process for translating embedded actions in Odoo. Previously, a manual translation step was required, but now that embedded actions automatically inherit translations from their linked actions, this step is no longer necessary. This streamlines the process and ensures consistent translations.

Now that `ir.embedded.actions` delegates its display name to the linked action, the manual translation copy on embedded action creation is no longer needed.

Related: https://github.com/odoo/odoo/pull/262981

Forward-Port-Of: odoo/enterprise#117772
Forward-Port-Of: odoo/enterprise#116369

This update resolves a test failure in the Odoo WhatsApp app's discuss sidebar. The change ensures the test accurately reflects the new system behavior of only considering active users when determining user IDs. This improves the reliability of the test and ensures the app functions correctly for users.

This PR updates the discuss sidebar testcase to match the new behavior
where only active users are considered when computing main_user_id, reducing the
number of available commands and fixing the failing assertion.

community: https://github.com/odoo/odoo/pull/262247 
task-6179486

Forward-Port-Of: odoo/enterprise#118063
Forward-Port-Of: odoo/enterprise#117480

This update ensures that quality checks are displayed only for the products actually picked within a stock picking. Previously, all products associated with a picking would trigger quality checks, even if only one was picked. This change improves efficiency and prevents unnecessary quality check generation.

*: stock_barcode_quality_control

Issue
---------------------------------
When a picking contains multiple products and each product has its own
operation-type quality point, opening the Quality Checks from the button
shows all quality checks, even for only one product is picked yet.

However, when validating the picking directly, only the picked products'
quality checks are shown.

Steps to reproduce
---------------------------------
- Create two products (Product A, Product B)
- Create one quality point per product with operation type and product_id set
- Create a receipt including both products
- Picked only Product A
- Click on the "Quality Checks" button
- Quality checks for both products are displayed instead of only Product A.

Cause
---------------------------------
The Quality Checks button uses `_is_checkable`, which calls
`_is_checkable_from_context`. This method always returns True unless the
context contains 'picking_validation'. That context key is only set during
the validation flow, so the button flow incorrectly shows all checks.

With this commit:
---------------------------------
Remove the unnecessary context-based condition and align the logic so that
both the Quality Checks button and the validation flow only consider picked
products.
Quality checks opened from the button or validation now behave consistently
and only include checks for products that are actually picked, preventing
irrelevant or premature quality checks.

Task ID: 4647113