This traceback arises when the user tries to delete `Work Locations`.

To reproduce this issue:

1) Install `hr_homeworking`
2) Open `Employees/Configuration/Work Locations`
3) Try to delete multiple records

Error:- 

```
ValueError: too many values to unpack (expected 3)
  File "odoo/http.py", line 2157, in __call__
    response = request._serve_db()
  File "odoo/http.py", line 1732, in _serve_db
    return service_model.retrying(self._serve_ir_http, self.env)
  File "odoo/service/model.py", line 133, in retrying
    result = func()
  File "odoo/http.py", line 1759, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "odoo/http.py", line 1960, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
  File "odoo/addons/base/models/ir_http.py", line 207, in _dispatch
    result = endpoint(**request.params)
  File "odoo/http.py", line 722, in route_wrapper
    result = endpoint(self, *args, **params_ok)
  File "addons/web/controllers/dataset.py", line 24, in call_kw
    return self._call_kw(model, method, args, kwargs)
  File "addons/web/controllers/dataset.py", line 20, in _call_kw
    return call_kw(request.env[model], method, args, kwargs)
  File "odoo/api.py", line 466, in call_kw
    result = _call_kw_multi(method, model, args, kwargs)
  File "odoo/api.py", line 453, in _call_kw_multi
    result = method(recs, *args, **kwargs)
  File "odoo/models.py", line 4160, in unlink
    func(self)
  File "addons/hr_homeworking/models/hr_work_location.py", line 17, in _unlink_except_used_by_employee
    exceptions_using_location = self.env['hr.employee.location'].search(('work_location_id', 'in', self.ids))
  File "odoo/models.py", line 1604, in search
    return self.search_fetch(domain, [], offset=offset, limit=limit, order=order)
  File "odoo/models.py", line 1627, in search_fetch
    query = self._search(domain, offset=offset, limit=limit, order=order or self._order)
  File "odoo/models.py", line 5366, in _search
    query = self._where_calc(domain)
  File "odoo/models.py", line 5081, in _where_calc
    return expression.expression(domain, self).query
  File "odoo/osv/expression.py", line 788, in __init__
    self.expression = domain_combine_anies(domain, model)
  File "odoo/osv/expression.py", line 597, in domain_combine_anies
    domain_any = _anyfy_leaves(domain, model)
  File "odoo/osv/expression.py", line 371, in _anyfy_leaves
    left, operator, right = item = tuple(item)
```

An invalid domain format is used when searching for the record in `hr.employee.location`.

See:

https://github.com/odoo/odoo/blob/def16f3725f8005874a18eb28b171523af1a0ecf/addons/hr_homeworking/models/hr_work_location.py#L17

sentry-4644429734

Forward-Port-Of: odoo/odoo#142866

Summary:
Being able to add withholdings in a user-friendly way. The 1st Phase will be mostly manual, and for other iterations, we can add more complex computation for the AR market specifically.

This is a legal requirement for many companies in AR that are withholding agents, where the company is meant to compute, create and share the Vendor WTHs (in this case the WTH is not electronic, but a PDF report with the details of the WTHs created need to be shared with the Vendor)

Conclusion & Scope:
- A first MVP will be released covering the basic use cases: 
- Manual allocation of Withholdings on the payment wizards

For 1st iteration it will be all manual, both for sales and purchases, we will work on the automation on the 2nd iteration of this feature.

This module adds 
- New taxes (withholding of IIBB and Earnings)
- A new group of withholding taxes
- Extends the payment register view to be able to add withholding taxes. 
- Extends the payment receipt document report to reflect the register withholding taxes




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

Forward-Port-Of: odoo/odoo#140607

This issue arises when attempting to edit the job location field for a remote job or when there is no value in the job location, try to edit and save record.

Steps to produce :
- Install `website_hr_recruitment` module.
- Open a job position that has a remote job location or no value in the job location.
- Open editor > Edit that field and save the record.
- Error will be generated.

see the traceback:
```
TypeError: int() argument must be a string, a bytes-like object or a real number, not 'NoneType'
  File "odoo/http.py", line 2139, in __call__
    response = request._serve_db()
  File "odoo/http.py", line 1715, in _serve_db
    return service_model.retrying(self._serve_ir_http, self.env)
  File "odoo/service/model.py", line 133, in retrying
    result = func()
  File "odoo/http.py", line 1742, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "odoo/http.py", line 1943, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
  File "addons/website/models/ir_http.py", line 235, in _dispatch
    response = super()._dispatch(endpoint)
  File "odoo/addons/base/models/ir_http.py", line 191, in _dispatch
    result = endpoint(**request.params)
  File "odoo/http.py", line 717, in route_wrapper
    result = endpoint(self, *args, **params_ok)
  File "addons/web/controllers/dataset.py", line 30, in call_kw
    return self._call_kw(model, method, args, kwargs)
  File "addons/web/controllers/dataset.py", line 26, in _call_kw
    return call_kw(request.env[model], method, args, kwargs)
  File "odoo/api.py", line 466, in call_kw
    result = _call_kw_multi(method, model, args, kwargs)
  File "odoo/api.py", line 453, in _call_kw_multi
    result = method(recs, *args, **kwargs)
  File "addons/website/models/ir_ui_view.py", line 485, in save
    super(View, self).save(value, xpath=xpath)
  File "addons/web_editor/models/ir_ui_view.py", line 175, in save
    self.save_embedded_field(arch_section)
  File "addons/web_editor/models/ir_ui_view.py", line 46, in save_embedded_field
    value = converter.from_html(Model, Model._fields[field], el)
  File "addons/web_editor/models/ir_qweb_fields.py", line 230, in from_html
    many2one_id = int(element.get('data-oe-many2one-id'))

```

This issue occurs because here
https://github.com/odoo/odoo/blob/5e0f5c98330ca1b5d0696c109c9e3a2050a6210c/addons/web_editor/models/ir_qweb.py#L215 it will get None and then when it will try to convert in int than error occurs.

after this commit user will not be able to edit the job location field.

sentry-4588277341

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

Forward-Port-Of: odoo/odoo#141825
Forward-Port-Of: odoo/odoo#140857

Since commit 3d218e1, clicking outside
a popover closes the popover and performs a preventDefault on the event. As a consequence, changes made in the property definition popover are no longer applied when the popover is closed by clicking outside.

Problem:
The preventDefault has the consequence of cancelling the input change event allowing the change to be applied to the property definition when the popover is closed.

Solution:
Remove the preventDefault by default and only use it in the case of the calendar view, which is the only use case that wants to prevent the click event so as not to open a record creation dialog (see commit 3d218e1).

How to reproduce the PropertyField bug:
- Go to a form view with a properties field
- Click on the edit property button
- A popover opens so that you can edit the field definition
- Type a few characters in the label input
- Click outside the popover

Before this commit:
    The value inserted in the popover is ignored

After this commit:
    The value inserted in the popover is applied to the property.

It is not possible to write a test reproducing this native browser behaviour.

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#142842

This fix reverts some changes of this commit : https://github.com/odoo/enterprise/commit/2711a3ad30bf306df35042d658c7b62a20fcb96f

Issue:
======
The planned hours in project timesheet forecast is counting the holdiays as working days too , so the displayed hours are wrong.

Steps to reproduce the issue:
=============================
Activate timesheets and planning in project setting. Create a product with the following values:
- Type : Service
- Create on order : Project & task
- Plan Services : active and select anything work planner for example
- Unit of Measure / Purchase UoM: Days Create a sale order with that product and choose 10 quantities and confirm it.

Click on smart button (8O hours to plan)
Click on new and select a resource and start and end date that have 80 alloctated time and save it.
Go to project , click on the 3 dots on the project related to the sale order and select Timesheets and Planning analysis
You will get more planned hours than expected , you can groupby day to see the planned hours for each day.

Origin of the issue:
====================
When creating the table we didn't take into account the calendar of the employee , so it will always count all days from start to end.

Solution:
=========
I reverted some of the changed of the commit mentioned above which was responsible for this.

opw-3482252
opw-3563938

Forward-Port-Of: odoo/enterprise#51120
Forward-Port-Of: odoo/enterprise#49901