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

Forward-Port-Of: odoo/odoo#230284

If a res_partner_bank record shares an acc_number with other res_partner_bank records, even archived ones, the field duplicate_bank_partner_ids still includes partners from those archived records.

As a result, the contact page shows a banner indicating other partners use the same bank account, even though those res_partner_bank records have been archived.

Steps to reproduce the issue:

1. Create a new bank account which has the same bank account number as another bank account already associated to a partner
2. Assign this new bank account to another partner
3. Archive this new bank account
4. Go to the contact page of the partner (from step 1) which has a bank account with the same bank account number as the new bank account just created
5. A banner will pop up at the top of the contact saying that this partner uses the same bank account as the partner you set on the bank account in step 2

Solution:

Add a condition to the JOIN clause that checks “other.active = TRUE” to ensure that other res_partner_bank records to search for that have the same account number are active.

Also add a condition to the WHERE clause that checks “this.active = TRUE” to ensure that the current res_partner_bank record doing the search is active itself.

opw-4967083

Forward-Port-Of: odoo/odoo#232018
Forward-Port-Of: odoo/odoo#231585

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

Forward-Port-Of: odoo/odoo#230284

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

Forward-Port-Of: odoo/odoo#230284

*: hr, web

Follow-up of https://github.com/odoo/enterprise/pull/98481

PR above added a new HOOT test in test_discuss_full_enterprise that is duplicate of a livechat tests, to cover good working of feature when overrides like `ai` module are applied in code.

It replaced a `defineHrModels()` into a
`defineTestDiscussFullEnterprise()`, which is shortcut for the test helper `defineWebsiteHelpdeskLivechatModels`. This is because the new test needs livechat models, and it's hard to combine defineModels for odoo modules that do not strictly patch on top of each other.

While it doesn't look like it, the test "can handle command and disable mentions in AI composer" sometimes asks for hr models and can fail non-deterministically because of that.

This commit fixes the issue by adding hr models in the helper of `test_discuss_full_enterprise`. To combine same models together with ease, instead of defining subclasses for extension, the models are instead patched. Since the patch is made in place, they combine nicely without puzzling with combining models in the right order, something that even the actual models in python don't have to care about.

Fixes https://runbot.odoo.com/runbot/build/92414152

*: test_discuss_full_enterprise

Follow-up of https://github.com/odoo/enterprise/pull/98481

PR above added a new HOOT test in test_discuss_full_enterprise that is duplicate of a livechat tests, to cover good working of feature when overrides like `ai` module are applied in code.

It replaced a `defineHrModels()` into a
`defineTestDiscussFullEnterprise()`, which is shortcut for the test helper `defineWebsiteHelpdeskLivechatModels`. This is because the new test needs livechat models, and it's hard to combine defineModels for odoo modules that do not strictly patch on top of each other.

While it doesn't look like it, the test "can handle command and disable mentions in AI composer" sometimes asks for hr models and can fail non-deterministically because of that.

This commit fixes the issue by adding hr models in the helper of `test_discuss_full_enterprise`. To combine same models together with ease, instead of defining subclasses for extension, the models are instead patched. Since the patch is made in place, they combine nicely without puzzling with combining models in the right order, something that even the actual models in python don't have to care about.

Fixes https://runbot.odoo.com/runbot/build/92414152