Product ribbon color changes in the eCommerce editor are now preserved after saving. This ensures shoppers see the intended promotional styling instead of the default color.

Issue
-----
Changing the color of the product's ribbon to a custome one in eCommerce has
no effect outside of the editor (after clicking "Save", the background color
of the ribbon returns to the default one).

Change
-----
Since the bg-primary class is now set on the ribbon HTML at creation.
https://github.com/odoo/odoo/blob/56fd8440707a0f3f2ba298f8bf016577ca08796b/addons/website_sale/static/src/js/website_sale.editor.js#L180
Remove the bg-primary class from the ribbon.

opw-4069818

Correcting Swedish translated Templates for Sale. Without this correction the swedish e-mails will crash. This solves the support tickit #3900977.

Correcting Swedish translated Templates for Sale. Without this correction the swedish e-mails will crash. This solves the support tickit #3900977.

This fixes how Japanese electronic invoices report a company's tax registration number. The system now uses the official qualified invoice registration number as expected, avoiding an incorrect country prefix that could cause compliance or validation issues.

At the moment, JP is added at the start of the tax scheme vals. In Japan and after 2023-10-01, the expected value in the company_id is the "Registration Number for Qualified Invoice purpose in Japan" which starts with a T and does not want JP prepended to it.

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

This update corrects internal performance test measurements for event email scheduling and mail templates. It helps ensure future scalability work is assessed against more realistic usage conditions, reducing the risk of misleading test results.

Fix query counters for event mail schedulers and mail template performance tests.

Use warmup decorator to remove queries linked to cold state, in order to have results closer to real life scenario.

Prepares Task-3084943: Event: Improve communication scheduler scalability

This fixes a Google Calendar synchronization issue where certain events missing start or end details could cause the sync to fail. Odoo now checks that those details exist before using them, making calendar updates more reliable for users.

Before this commit, accessing start and stop values directly from new event values could lead to a KeyError if these keys were missing. This commit adds a safeguard to prevent such errors by checking for the existence of these keys before attempting to access them, ensuring a more robust handling of event data.

Here is traceback:
```
  File "/home/odoo/src/odoo/addons/google_calendar/controllers/main.py", line 46, in google_calendar_sync_data
    need_refresh = request.env.user.sudo()._sync_google_calendar(GoogleCal)
  File "/home/odoo/src/odoo/addons/google_calendar/models/res_users.py", line 73, in _sync_google_calendar
    synced_recurrences = self.env['calendar.recurrence'].with_context(write_dates=recurrences_write_dates)._sync_google2odoo(recurrences)
  File "/home/odoo/src/odoo/addons/google_calendar/models/google_sync.py", line 197, in _sync_google2odoo
    odoo_record.with_context(context)._write_from_google(gevent, vals)
  File "/home/odoo/src/odoo/addons/google_calendar/models/calendar_recurrence_rule.py", line 122, in _write_from_google
    if old_event_values and any(new_event_values[key] != old_event_values[key] for key in base_event_time_fields):
  File "/home/odoo/src/odoo/addons/google_calendar/models/calendar_recurrence_rule.py", line 122, in <genexpr>
    if old_event_values and any(new_event_values[key] != old_event_values[key] for key in base_event_time_fields):
KeyError: 'start'
```

opw-4100958

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

This update fixes the visual styling of appointment descriptions in the Odoo Appointments module. The styling issue has been corrected to ensure appointment details display properly for users booking appointments.

Commit fixes appointment description styling

task-3446959

This update corrects the Spanish translation for "Colony code" in the Mexican EDI module from "Código postal" (postal code) to "Código de colonia" (colony code). This ensures accurate terminology for Mexican users when processing electronic invoices, improving clarity and compliance with local standards.

"Colony code" translation changed from:
"Código postal" => "Código de colonia"