Steps to reproduce on runbot:
1. Select company "My Belgian Company" (`l10n_be` and `account_peppol`) should be installed
2. Settings -> Accounting -> PEPPOL Electronic Invoicing -> Activate Electronic Invoicing
3. Ensure `+32470123456` is given as the phone number
4. Remove the country prefix from the phone number
5. A validation error is raised complaining about the phone number format

The validation should only be performed when we click on the "Activate Peppol" button.. When editing the phone number the wizard should try to auto-format the given phone number before validating.
In case there is no country prefix it should assume the phone number is from the country of the company.

Since commit 7cd8c87e3fcacfefa6c789449eec32a3c5577089 the validation is performed before the auto-formating. There a call to the validation logic (`_sanitize_peppol_phone_number`) was added before the auto-formatting logic. (It was mainly just done to ensure that an external dependency is installed.) But there we do not (and should not) assume the country prefix of the phone number. The phone number is used during the registration process. A missing country prefix could lead to a failed registration.

After this commit
- the validation is only performed when we click on the "Activate Peppol" button.
- the auto-formatting is performed after editing the phone number
- the changes are not stored on the company when clicking on "Discard"
- fix a `self` in a `for ... in self`

part of
task-4791098

**Problem:**
When changing the price type of a Discount pricelist rule to 
"formula" and going back to the original price type "discount"
the rule does not take into account the base pricelist anymore
and uses the list price of the product to compute the discount

**Steps to reproduce:**
- Navigate to Sales/Products/Pricelists
- Create a new pricelist, click on Add a line
- In "Price Type" select Fixed Price and set a Fixed Price of 10
- Save and Close > create a second new price list
- Click on "Add a line" and select a Price Type Discount
- Set a 50% discount percent and select your first pricelist
as the base price (next to "on")
- Save and Close > save the form
- Open the rule again and change the Price Type to formula 
- Change the Price Type back to Discount and set a discount percentage
of 50% again
- Save and Close
- Create a new quotation with a product and select the second pricelist
you created > click on Update Prices

**Current behavior:**
 Amount is 50% of the price of the product 

**Expected behavior:**
It should be 50% of 10 because our second pricelist is based on the 
first one which has a fixed price of 10

**Cause of the issue:**
when _onchange_compute_price is triggeredwhen going back 
to discount value, base will be set to list_price
https://github.com/odoo/odoo/blob/d3e43681fd2b989ae7272731662cc3ac6a6d913b/addons/product/models/product_pricelist_item.py#L334-L342
because of this, the base price will not be computed based on the 
base pricelist 
https://github.com/odoo/odoo/blob/d3e43681fd2b989ae7272731662cc3ac6a6d913b/addons/product/models/product_pricelist_item.py#L580-L583

**fix:**
By resetting the base_pricelist_id, it's now visible to the user
on the form that the computation is no more based on a pricelist.
If the user enters a pricelist, the correct value will be computerd
for base and base_pricelist_id at that time.

opw-4757951

Problem:
Adding a document when creating a new email template using `/media`
results in duplicated content on save.

Cause:
During HTML processing on save, `flattenBackgroundImages` wraps
elements with inline background images (`style*=background-image`)
in MSO-specific comments: `<!--[if mso]><![endif]-->`.

However, if multiple such elements are nested, they are each wrapped,
resulting in invalid nested comments and broken layout.

Solution:
Since the two conditions are opposites, we remove completely the content
of the nested comment if it has oppisite condition otherwise we just
remove the comment tags since they will be replaced with the upper
comment

Fixed in `web_editor` in https://github.com/odoo/odoo/commit/fcedeb63f5b5da6758e75d02f0c1d4f3b965adc1

Steps to reproduce:
1. Create a new email template.
2. Add a document using `/media`.
3. Save.
→ The content is duplicated or layout is broken.

opw-4775908

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

### Steps to reproduce:

- Have 2 companies: COMP1 and COMP2
- Create a storable product P with a kit bom for attached to COMP1.
- With COMP2 create a delivery for 1 unit of P.
> If you click on check availability the move should not be assigned.
- As COMP1 and with COMP2 active, click on check availability once more
#### > The move is assigned.

### Cause of the issue:

Checking the availability will launch a call of the `action_assign` of the stock picking. During this call, the moves that shoudl by pass the reservation process will automatically be reserved: https://github.com/odoo/odoo/blob/9b0c1c416eaa0df64fbe28c5672f2590a218f315/addons/stock/models/stock_move.py#L1852-L1853 However, kit products are flagged to bypass the reservation process by these lines:
https://github.com/odoo/odoo/blob/9b0c1c416eaa0df64fbe28c5672f2590a218f315/addons/mrp/models/stock_move.py#L521-L522 The issue with this line being that the product is a kit form COMP1 and not for COMP2 (the context is used to determine this in the compute method):
https://github.com/odoo/odoo/blob/9b0c1c416eaa0df64fbe28c5672f2590a218f315/addons/mrp/models/product.py#L38-L40

### Note:

The issue can not be reproduced prior to 18.0, since the override of the `_should_bypass_reservation` was introduced by commit 4e1d46869e6c2d1ff473317179393007522a10a3

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