When the user changes the language in My Profile and tries to save,
a traceback will appear.

Steps to reproduce the error:
- Install ```account_accountant``` and ```hr``` module
- Activate multi languages
- Go to accounting > Dashboard > New Invoice
- Click on the profile icon > My Profile > Change language > Save

Traceback:
```
ValueError: too many values to unpack (expected 1)
  File "odoo/models.py", line 5851, in ensure_one
    _id, = self._ids
ValueError: Expected singleton: account.move('n', 'e', 'w')
  File "odoo/http.py", line 2254, in __call__
    response = request._serve_db()
  File "odoo/http.py", line 1829, in _serve_db
    return self._transactioning(_serve_ir_http, readonly=ro)
  File "odoo/http.py", line 1849, in _transactioning
    return service_model.retrying(func, env=self.env)
  File "odoo/service/model.py", line 134, in retrying
    result = func()
  File "odoo/http.py", line 1827, in _serve_ir_http
    return self._serve_ir_http(rule, args)
  File "odoo/http.py", line 1834, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "odoo/http.py", line 2059, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
  File "odoo/addons/base/models/ir_http.py", line 220, in _dispatch
    result = endpoint(**request.params)
  File "odoo/http.py", line 740, in route_wrapper
    result = endpoint(self, *args, **params_ok)
  File "addons/web/controllers/action.py", line 96, in load_breadcrumbs
    display_names.append(Model.browse(record_id).display_name)
  File "odoo/fields.py", line 1202, in __get__
    record.ensure_one()
  File "odoo/models.py", line 5854, in ensure_one
    raise ValueError("Expected singleton: %s" % self)
```

https://github.com/odoo/odoo/blob/59985860264f7fbd2726a51ff15d7e5101ae8234/addons/web/controllers/action.py#L97
Here, when the user changes the language and tries to save the record.
we received record_id as ('n', 'e', 'w'),
when it tries to access display_name
So it will lead to the above traceback.

This issue is similar to https://github.com/odoo/odoo/pull/163087

sentry-5135218331

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

If we have two bills with the same bill ref and two different partner, one with NIF and the other without it, the schedule action to process SII response might fail since the code expect a NIF in the SII response when there is not (bill with partner without NIF).

Technical example:
```py
>>> partner_info # Candidate invoice in odoo
{'IDOtro': {'ID': 'NO_DISPONIBLE', 'IDType': '06', 'CodigoPais': 'ES'}}
>>> respl_partner_info # SII response
{'NIF': '12345678K', 'IDOtro': None}
```
This causes a rollback and no bills at all are processed in Odoo's side.

Steps to reproduce:
1/ Create a l10n_es company with l10n_es_edi_sii in test mode
2/ Create a bill with a bill reference 10001, some lines (ex: negative lines)
     that will trigger an error from SII and a partner with a NIF
3/ Copy the partner and remove the NIF
4/ Copy the first bill, keep the same bill reference and change the partner to
     copied one
5/ Post both bills
6/ Trigger the schedule action "EDI : Perform web services operations" => Traceback with
ValueError: <class 'AttributeError'>: "'NoneType' object has no attribute 'ID'" while evaluating

Now, a default value is set when the key is not found in respl_partner_info.IDOtro .

opw-4102638

Forward-Port-Of: odoo/odoo#177902

Currently, when adding product rewards to an order, you are rewarded with the maximum amount of products you can get with you current points. If you change the quantity of the reward product, the reward lines does not update.

Steps to reproduce:
-------------------
* Go to the **Point of sale** App
* Open Shop session
* Select a customer that has plenty of loyalty points
* Put any product in the order
* Add the reward `Simple pen` (you'll havelike 230 of them)
* Try changing the reward quantity to 1
> Observation: The quantity of the simple pen changes to 1 but the negative reward line still shows 230. Thus, the order can have a negative amount since 229 pens are still being deducted from the order even though they are not present.

Why the fix:
------------
This commit https://github.com/odoo/odoo/commit/de45ff3c9f23decdab176bc1511b3356d19844a8 passes the quantity and cost (in points) to the `_applyReward` function. This was done because when recomputing reward lines, if two lines came from the same reward, the quantity would be merged even though they would not apply on the same product.

In our case, this causes problems as we are using the function `_getRewardLineValuesProduct` to update the reward quantity but the quantity (230) is given as an argument and is then used as the quantity to set.
https://github.com/odoo/odoo/blob/775827b8f7fa95f2afd77a9b42d6cd8e436ea690/addons/pos_loyalty/static/src/overrides/models/loyalty.js#L1548-L1566

`args["quantity"] || freeQuantity` will always use `args["quantity"]` if given, bypassing the maximum quantity that is available to give.

`freeQuantity || args["quantity"]` will never use `args["quantity"]`.

Since we do not want to reward more than what is available, we add the arguments inside the `Math.min` function.

opw-4103833

Forward-Port-Of: odoo/odoo#178805

Current behavior before PR:

1. When we attempt to paste an H1 element into a P element, the H1 element gets converted to a P element.
2. When pasting from GDocs, nested UL or OL is a direct child of its parent UL or OL, rather than being child of LI with class `oe-nested`.
3. Copy/pasting multiple paragraphs into a list does not convert it to list.
4. When pasting content that begins with a list and includes other tags below it into a new list, only the list is pasted, resulting in a loss of the other content.
5. Copy/pasting one list over another bullets does not get transformed.
6. When copying a checklist from Google Docs, the check options are pasted as images.

Desired behavior after PR is merged:

1. When we attempt to paste an H1 element onto a P element, the H1 element will remain as an H1 element.
2. When pasting from GDocs, nested UL or OL are contained within an LI element with class `oe-nested`.
3. Copy/pasting multiple paragraphs into a list gets converted to list.
4. Pasting content with a list and other tags should no longer result in the loss of content.
5. Copy/pasting one list over another bullets get transformed.
6. Check options copied as image from Google Docs will no longer be pasted as images; instead the images should be removed and class `o_checklist` should be add to the closest list.

task-2956048

Co-authored-by: Deependra Solanki <deso@odoo.com>

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

Forward-Port-Of: odoo/odoo#179159
Forward-Port-Of: odoo/odoo#115019

In makeAsyncHandler and makeButtonHandler have been modified in commit fcb16a3b1bd373726ffb54f0fbe41fb6d1784769 to remove guardedCatch.

However, in both cases, if result is rejected, Promise.resolve(result) will (quite unexpectedly because of the name of the method) be rejected too. Calling finally on this promise will indeed call the callback, but it will still let the exception bubble up, eventually resulting in a second unhandledrejection for the same original exception.

With this commit, we instead call then(callback, callback) on that Promise, so that the rejection is caught and callback is indeed called in both cases.

To reproduce this issue in saas-17.4, raise a UserError in the route /website_sale/should_show_product_configurator and add a Drawer to your cart: the exception message is displayed twice.
This reproduction doesn't work in 17.0 because the promise is a dialog.opened() that crashes and never resolves, masking the issue (but there is a hint of this, because the loading effect is also never removed from the button (meaning that the callback of makeButtonHandler is never called). Many thanks to MCM to help me understand what was happening here.

Forward-Port-Of: odoo/odoo#179512

[FIX] project: restrict access to project in email sent

Before this commit, when the `Project Stages` feature is enabled and the
user set an email template on a project stage, if the user moves a
project to that stage with the email template, an email is sent to the
customer (if set on the project) and the customer can click on the project name
to see all tasks inside that project even if the project is private.

This commit makes sure the project name displayed in the template is
only clickable is the project visibility is 'portal'
(`Invited portal users and all internal users`).

Steps to reproduce:
------------------
1. Install project
2. Go to Project > Configuration > Settings
3. Enable Project Stages feature
4. Set email template to project stage
5. Create a project with a customer set and project visibility is not
   set to "Invited portal users and all internal users".
6. Move the project to the project stage with the email template set.

Current behavior:
----------------
An email is sent based on the email template set but the project name is
clickable to allow the customer to see the tasks of the project in the
portal even if the project is not public.

Expected behavior:
-----------------
The project name should not be clickable inside the email sent when the
project visibility is not "Invited portal users and all internal users".

Close #175396

Forward-Port-Of: odoo/odoo#178260
Forward-Port-Of: odoo/odoo#178171

### Steps to reproduce:

- In the settings:
  - Change the Barcode Nomenclature to Default gs1
  - Enable Promotions, Coupons, ... on Point of sale
- Create a prodcut with barcode 95412427100283
- Point of Sale > Product > Discount & Loyalty
- Create a new discount and change the conditional rule to set your product and a min purchase of 0
- Open a new pos session
- Scan the gs1 barcode 0195412427100283

#### > the product is found but the discount is not applied

### Expected behavior:

Just as if you scanned the barcode 95412427100283 directly the discount should be applied.

Cause of the issue:

When a barcode is scanned in the pos, the ` _scan` method is called to parse the barcode and to trigger the associated action:
https://github.com/odoo/odoo/blob/775827b8f7fa95f2afd77a9b42d6cd8e436ea690/addons/point_of_sale/static/src/app/barcode/barcode_reader_service.js#L69-L79
This flow use to not update the rewards after a product scanned and was fixed by commit 21392ab when the barcode associated action is `_barcodeProductAction` because fo these lines:
https://github.com/odoo/odoo/blob/775827b8f7fa95f2afd77a9b42d6cd8e436ea690/addons/pos_loyalty/static/src/overrides/components/product_screen/product_screen.js#L105-L107 however, if the code is identified to be gs1
Howecver, if the barcode is identified to be of the gs1 nomenclature it will trigger the `_barcodeGS1Action` which still does not update the rewards.

### Fix:

Inspired by commit 21392ab

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

Forward-Port-Of: odoo/odoo#178600