## Description
`component_qty_to_do` is computed based on `qty_done` & `component_remaining_qty`, which both use the same decimal accuracy 'Product Unit of Measure'. Without this decimal accuracy set on `component_qty_to_do`, the view `quality_check_view_form_tablet` can misinterpret the actual value, and will show an incorrect action to do ('continue production' instead of 'validate').

## To Reproduce:
https://watch.screencastify.com/v/S3pT4bV1u29a2EbLxX8R
- Create a product FNS & a component CMP.
- Create a BOM for FNS:
    - Using 13.2 units of CMP
    - Flexible Consumption to 'Blocked' (under Miscellaneous)
    - 1 operation
- Add a step to the operation with:
    - Type: 'Register Consumed Materials'
    - Product to register: CMP
- Create a Manufacturing order for 1 unit of FNS -> Confirm -> Plan
- Go to the workorder tablet view:
==> The qty_done should be set to 13.2, but the button shown is still 'Continue Production' instead of 'Validate'.


If the  component quantity is different (ex: 13), here is how it looks like when you open the workorder tablet view:
![image](https://github.com/odoo/enterprise/assets/29302288/1c0040e2-1396-4aef-9a58-22200986a173)


---

OPW-3322942

Forward-Port-Of: odoo/enterprise#41710

When user create new employee payslip, select employee and remove date of ```date_to``` field,
a traceback will appear.

Steps to reproduce the issue:
- Go to Payroll > Payslips > All Payslips
- Create New Employee Payslip
- Select any Employee
- Remove date of ```date_to``` field.

Traceback:
```
KeyError: <NewId 0x7f3063ad3eb0>
  File "odoo/api.py", line 959, in get
    cache_value = field_cache[record._ids[0]]
CacheMiss: 'hr.payslip(<NewId 0x7f3063ad3eb0>,).is_wrong_duration'
  File "odoo/fields.py", line 1158, in __get__
    value = env.cache.get(record, self)
  File "odoo/api.py", line 966, in get
    raise CacheMiss(record, field)
KeyError: <NewId 0x7f3063ad3eb0>
  File "odoo/api.py", line 959, in get
    cache_value = field_cache[record._ids[0]]
CacheMiss: 'hr.payslip(<NewId 0x7f3063ad3eb0>,).is_wrong_duration'
  File "odoo/fields.py", line 1213, in __get__
    value = env.cache.get(record, self)
  File "odoo/api.py", line 966, in get
    raise CacheMiss(record, field)
ValueError: Compute method failed to assign hr.payslip(<NewId 0x7f3063ad3eb0>,).is_wrong_duration
  File "odoo/http.py", line 2123, in __call__
    response = request._serve_db()
  File "odoo/http.py", line 1699, 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 1726, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "odoo/http.py", line 1927, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
  File "odoo/addons/base/models/ir_http.py", line 190, in _dispatch
    result = endpoint(**request.params)
  File "odoo/http.py", line 716, 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 461, in call_kw
    result = _call_kw_multi(method, model, args, kwargs)
  File "odoo/api.py", line 448, in _call_kw_multi
    result = method(recs, *args, **kwargs)
  File "odoo/models.py", line 6704, in onchange
    todo = [
  File "odoo/models.py", line 6707, in <listcomp>
    if name not in done and snapshot0.has_changed(name)
  File "odoo/models.py", line 6504, in has_changed
    return self[name] != record[name]
  File "odoo/models.py", line 6131, in __getitem__
    return self._fields[key].__get__(self, type(self))
  File "odoo/fields.py", line 1155, in __get__
    self.recompute(record)
  File "odoo/fields.py", line 1365, in recompute
    apply_except_missing(self.compute_value, recs)
  File "odoo/fields.py", line 1338, in apply_except_missing
    func(records)
  File "odoo/fields.py", line 1387, in compute_value
    records._compute_field_value(self)
  File "addons/mail/models/mail_thread.py", line 396, in _compute_field_value
    return super()._compute_field_value(field)
  File "odoo/models.py", line 4491, in _compute_field_value
    fields.determine(field.compute, self)
  File "odoo/fields.py", line 99, in determine
    return needle(*args)
  File "home/odoo/src/enterprise/saas-16.3/hr_payroll/models/hr_payslip.py", line 892, in _compute_name
    'dates': slip._get_period_name()
  File "home/odoo/src/enterprise/saas-16.3/hr_payroll/models/hr_payslip.py", line 841, in _get_period_name
    if self.is_wrong_duration:
  File "odoo/fields.py", line 1216, in __get__
    raise ValueError("Compute method failed to assign %s.%s" % (record, self.name))
```

https://github.com/odoo/enterprise/blob/cd42b0de992cc2acc8a403c828c06cf9501a3c6c/hr_payroll/models/hr_payslip.py#L840 Here, when user remove date of date_to field in employee slip,
It will not get any value for date_to field, when it will return period_name.
So it will lead to above traceback.

sentry-4306109394

Forward-Port-Of: odoo/enterprise#43914

Steps to reproduce:
-------------------
- go to the form view of a Payslip;
- click on the action menu "Edit Payslip Lines";
- add a line and fill with values;

Issue:
------
A traceback appears saying the component is destroyed.

Cause:
------
When we click on "Add a line", we create a `PayslipLineField` component for each field in the list view.

The purpose of the `fieldComponentProps` getter is to render the component props with the record, which has a new update method. We will redefine an update function for this record. It will be redefined only once, via the `isPayslipLineField` flag.

We will use the first component to be created for the record, i.e. a component for the `sequence` field.
The new update method uses `this` to make an orm call.

As a result, this will refer to the component
for the `sequence` field necessarily,
as we are defining this new update method only once.

Unfortunately, the record is in edit mode and
the `sequence` field component is not yet mounted.
 The component will therefore be destroyed
 during the "switchMode" method.

Without the `isPayslipLineField` flag,
it was "lucky" that the component existed
(the `this` was a component referring to the `total` field).

Solution:
---------
Use a component that does not refer to the `sequence` field, so that the call can be made with a mounted component.

Note:
-----
The problem does not append for records in the `WorkedDaysField` component, because the first field is `WorkedDaysField` and not a `sequence`.

opw-3419064

Forward-Port-Of: odoo/enterprise#43979

Steps to reproduce
==================

- Open a crm.lead form
- Open studio
- Switch to the "Extra Information" page
- Drag the "Company name" field somewhere else

-> The original field stays at the same place

Cause of the issue
==================

The simplified view is the following:

```xml
<form>
  <sheet>
    <group>
      <group name="lead_partner" attrs="{'invisible': [('type', '=', 'opportunity')]}">
        <field name="partner_name"/>
      </group>
    </group>
    <notebook>
      <page string="Extra Information" attrs="{'invisible': [('type', '=', 'lead')]}">
        <field name="partner_name"/>
      </page>
    </notebook>
  </sheet>
</form>
```

The following operation was send to the server

```py
{
    "type": "move",
    "target": {...},
    "position": "after",
    "node": {"tag": "field", "attrs": {"name": "partner_name"}},
}
```

Only the following attributes are use to differentiate fields: ['name', 'widget', 'options', 'display', 'optional']. This is not enough. In this case, we wanted to move the second occurence of the partner_name field, but the first one was actually moved.

Solution
========

Pass the xpath of the source field for the move operation.

opw-3270165

Forward-Port-Of: odoo/enterprise#43825
Forward-Port-Of: odoo/enterprise#43308