This PR adds a Select component that has been used here to replace
the jquery select2.
Other components and hooks have been used or modified to bring this
action to a better state, such as the UI service and BlockUI component, to
support custom messages and the use of components. It was required to
reimplement the loading progress and indicator used by the view.

The main goal of this PR is to reimplements the import action view to use Owl
instead of legacy code + library. Different components have been created to
separate the UI in smaller blocks, and a model file contains the main
aspects of the import logic.

The set_file route in the base_import controller has been adapted to remove
the usage of jsonp type of code for this situation since it is no longer
needed nowadays.

On top of the rewrite, js tests have been added to make sure the feature
behaves correctly, and to assert the intended specs.

Finally, legacy files + library have been removed, since they are no longer required.

This work has been done by @BastienFafchamps and myself

task-3092474

Prior to this commit, adding an anchor using auto-complete would not
properly prefix the url with the URL of the current page.

Steps to reproduce:
- Create a page (e.g. /test), add blocks and create an anchor (e.g.
#anchor)
- Save the page
- Click on "Edit Menu" in "Pages"
- Add a new menu entry
- Type '#' in the URL field and select the anchor
- Save

=> The menu entry is wrongly set as it does not contain the original
page's URL inside the `href` attribute. This means that clicking on the
menu from any other place will not properly redirect to the anchor on
the /test page

On top of that, editing a menu entry that was previously linked to a
page would change the URL of the page with an anchor, making it
impossible to access the page anymore until you change the URL back in
the page manager.

Steps to reproduce:
- Create a new page (e.g. test)
- Add a new menu entry that has this page as its URL
- Save the new menu entry (close the dialogs)
- Re-open the Menu dialog and edit the newly created menu entry
- In the URL field, replace it with the page + an anchor
 (e.g. /test#anchor)
- Save
=> The page's URL is now /test#anchor and is no longer accessible

The is due to the `save` method of the `website.menu` model not
containing code to properly manage adding an anchor to the menu.

This commit fixes that.

opw-3067750

Forward-Port-Of: odoo/odoo#108217
Forward-Port-Of: odoo/odoo#106882

The field `notified_partner_ids` has type Many2many with relation table
    `mail_message_res_partner_needaction_rel` [1] which is a regular Odoo model
    `mail.notification` with some extra fields. One of those fields is required:
    `notification_type`.

On copying `mail.message` record, ORM copies Many2many fields directly without using `default_get` method for `mail.notification` model. Particularly, `notification_type` get null value and we get an error.

STEPS

1. Create Server Action for `mail.message` model:

```py
for message in (records or record):
    message.copy({
        "subject": message.subject + "(SA copied)",
    })
```

2. Add contextual action
3. Open `mail.message` which has non-empty value on `notified_partner_ids` (*Partners with Need Action*)
4. Run the Server action via Action menu.

PROBLEM

```
ValueError: <class 'psycopg2.errors.NotNullViolation'>: "null value in column
"notification_type" of relation "mail_notification" violates not-null constraint
DETAIL: Failing row contains (11, 210, null, 3, null, null, null, null, null,
null, null, null, null).
```

SOLUTION

Fix it by adding `copy=False`, because we don't want to copy those values anyway (confirmed by TDE).

[1]: The relation table is renamed to `mail_notificaiton` in v15+

opw-3069556

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

Forward-Port-Of: odoo/odoo#108381
Forward-Port-Of: odoo/odoo#108295

To Reproduce
============

- enable QR code on Accounting settings
- with a vendor who has a bank account create an invoice from him/her
- print or preview the credit note

The Problem
===========

the qr code method field will not be filled with SEPA, and a QR code will not be added to the PDF or preview. This qr reflects the vendor's bank account, so the user could scan it and send the money. This feature was removed by PR #104496 because it was also printed in the refunds to the customers, which was odd, but as a side effect it is also removed from vendor bills.

Solution
========
The QR should not be hidden in vendor bills and purchase receipts, ( also in vendor refund it can be helpful for the vendor, but there isn't any complain about it now ) A better solution would be displaying the QR code in the form view if it is not the company's bank account (it is the partner's bank account), but it should be done in master, it is too much of change for stable versions.

Ticket No: 3071310


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

Forward-Port-Of: odoo/odoo#108484
Forward-Port-Of: odoo/odoo#108098

Commit [1] added a snippet template cache so that if a user changes pages on their website, they do not need to fetch the SnippetMenu from the server again.

Unfortunately that commit added a few side effects that commit [2] tried to fix since commit [3] made them apparent. However, there is still one broken flow:

- Create a website with 2 languages, e.g. English (primary) and French.
- Visit the website in French and enable translate mode
- Save and click on the "Edit in Master" button
- Drag and drop a Snippet
- The Snippet is in the translated language

This commit fixes this broken flow by clearing the snippet cache when changing the language of the website.

[1]: https://github.com/odoo/odoo/commit/03c552690b15cbf2e7d6b7812386ac64042219af#diff-52a4f9d2c217548e69e6b7fd097f286f1754a6389734eea254b87255e501cbefR18 
[2]: https://github.com/odoo/odoo/commit/bb503962a36f3798c50049f2844e7b288b632955 
[3]: https://github.com/odoo/odoo/commit/55a978aa86967581956f855a1c5db33b7425bd15

task-2687506

Forward-Port-Of: odoo/odoo#104140

changed boolean logic to set QC title based on whether QCP exists or not

Problem: The title of the quality checks is not the same as the title from the quality control point. It should use the title of the QCP if a title is set. Otherwise, it will create a title based on the QCP type and component

v13: https://github.com/odoo/enterprise/blob/060b07d69e57e983311ec50bc17aeeee70eaa601/mrp_workorder/models/quality.py#L137
The logic is to use the title of the QCP if there is a QCP; otherwise, create a title based on the QC type and component

v15: https://github.com/odoo/enterprise/blob/69be8a8261c9b253459262d15b236881712bef7d/mrp_workorder/models/quality.py#L208
The code from v13 was refactored but used the wrong boolean condition:
**Currently**: If there is no QCP or if there is a component, create a title based on the QC type and component 
**Error**: regardless of whether there is a QCP or not, it will always create a new title if there is a component
**Expected**: it should only create a title if there is no QCP
**Proposed Change:** Change the condition to use AND instead of OR --> it will short circuit by checking first whether there is a QCP or not. It will only create a new title if there is no QCP AND there exists a component

Steps to Reproduce on Runbot 15:
1.  Install Manufacturing, quality > enable Work Orders
2. Create C1, storable, buy
3. Create P1, storable, manufacture
4. Create a BOM for P1 > set type to Manufacture and use C1 as a component
5. Create a work order operation for P1 using the BOM from Step 4
6. Create a Quality Check Point for P1
- Set the title
- set Operations to Manufacturing
- Set Work Order operation to the one from Step 5
- Set Type to Register Consumed Materials
- Set Product to Register to C1
7.  Create an MO for P1 , Confirm, Finish the Work order
8. View Finished Steps from the finished WO and the Title is not the same as the QCP title

opw-3032479

Forward-Port-Of: odoo/enterprise#35189
Forward-Port-Of: odoo/enterprise#34777