This fix updates Odoo's email server handling and related tests so they work reliably on newer Debian Trixie environments. It prevents compatibility warnings and connection issues that could affect email-related setup or automated checks during deployments.

Adding contacts to a mailing list through the bulk wizard now records the subscription date correctly. This keeps contact history consistent regardless of whether users add contacts one by one or in bulk.

Steps to reproduce:
-------------------------
1. Install Email Marketing Module
2. Create a new Mail List
3. Go to Mailing List Contacts
4. Select multiple contacts from list and click on Add to List button
5. From wizard select the newly created list and click on Add button
6. Open one of the contact added in step 4

Observation:
-------------------------
In the Mailing Lists tab of the contact, the newly added list does not show a Subscription Date. However, if we add the same through Add a line, the subscription date is shown correctly.

Issue:
-------------------------
When adding contacts to a mailing list through the wizard, the code https://github.com/odoo/odoo/blob/1e6ba783fcd898875dadb47924147688685707cf/addons/mass_mailing/wizard/mailing_contact_to_list.py#L34-L39 adds the contact using a direct database operation. This bypasses the ORM record creation for `mailing.subscription`, so the `create_date` (subscription date) is never set.

Solution:
-------------------------
Use `Command.create` on the `subscription_ids` field to properly create the `mailing.subscription` records and ensure the Subscription Date is set.

opw-5055372

The Planning app now shows the recurring shift banner only after recurring shifts have actually been generated. This avoids confusing users with a banner that previously appeared before it could have any practical effect.

**Steps to reproduce:**
---------
1. Create a shift.
2. Save the shift.
3. Open the shift and enable the recurrence.
4. Observe that the recurrence banner is immediately displayed.

**Issue:**
-----
The recurrence banner is shown as soon as a shift is marked recurring, even though no recurring shifts have been generated yet. This is misleading since the banner has no effect until the actual recurrence slots exist.

**Cause:**
-------
The banner visibility was based on repeat and id, so it appeared too early, before any recurring shifts were actually created.

**Fix:**
--------
Update the banner visibility condition to check for both repeat and recurrency. Now, the recurrence banner only appears once the recurrence record exists and recurring shifts are generated:

task-5163851

Dimona-related employee fields now appear only when they are relevant to Belgian employees. This reduces confusion for companies managing employees in other countries and keeps employee records cleaner.

Before this commit, the fields about dimona were shown for all employees, now these fields will be displayed only for belgian employees.

task-5148931

Forward-Port-Of: odoo/enterprise#96496

This fix updates the online shop, wishlist, comparison, and reorder flows to use Odoo’s standard redirect mechanism when sending shoppers to another page. This helps make navigation more consistent and reduces the risk of redirect-related issues during ecommerce actions.

Enterprise PR: https://github.com/odoo/enterprise/pull/98492

The online rental shopping pages now use Odoo’s standard redirect mechanism when sending visitors to another page. This helps keep navigation behavior consistent and reduces the risk of broken or unreliable redirects during the shopping flow.

Community PR: https://github.com/odoo/odoo/pull/233842

This change fixes an internal automated test for the website editor so it waits correctly before checking link fields. It helps prevent false failures during busy test runs, improving confidence in release validation without changing user-facing behavior.

This test was not awaiting each step properly, which becomes visible when the runbot is overloaded and the querySelector calls return null, at which point accessing `click` or `value` would trigger a traceback.

runbot-161423

This pull request adds a signed Contributor License Agreement record for a contributor. It helps ensure Odoo has the necessary legal permission to accept and maintain the contributor's work.

closes odoo/odoo#232788

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




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