## Issue:
When configuring an employee before sending the salary configurator, if we set up children and disabled children for the employee, the option to enable/disable them in the salary configurator does not appear.

## Steps To Reproduce:
- on the runbot change the company to "my Belgian company".
- In Laurie Poiret's employee profile, on the "personal information" tab, change the value for children to 2 and set 1 as disabled.
- Go to Laurie Poiret's contract (stat button) and generate an offer.
- From the offer, navigate to the salary configurator.
- In the salary configurator, proceed until you reach the family status section.
- Notice that the "Disabled children" Toggle does not appear unless you change the value of the children input.
## Solution:
- The `onchangeChildren` method is being invoked in the `start` method without an `event` argument (`event` is `undefined`). This results in `event.currentTarget` being `undefined`, causing the `childCount` variable to be `NaN` and `disabledChildrenNumber` to get disabled at the end of the method.
- to fix the problem, we added a check for `event` argument in the event handler, if it is not present, we fallback to getting the children input value using JQuery and it solves the issue.

**opw-3925640**

Forward-Port-Of: odoo/enterprise#64347
Forward-Port-Of: odoo/enterprise#63535

**Steps to reproduce:**
- Go to list view or kanban view.
- Select the document to preview in the inspector.
- Clear the input value of a required field (here, Name or Workspace), and click elsewhere or press 'Enter'.

**Issues:**
- _**Workspace field**_
  A validation error is raised when a Workspace name is cleared. However, an alert dialog is not displayed.

- _**Name field**_
 An alert dialog indicating a validation error is shown yet on clicking the `OK` button, the unnamed document is saved as is.
  
  Instead, the changes should be reverted.

**Causes:**
- _**Workspace field**_
  The `required` attribute was not added to `folder_id` field in the view. As a result, alert dialog was not shown.

- _**Name field**_
  The config mode never changes to 'edit'. Even when a user is editing an inspector field, the mode is 'readonly'. 
  As a result, the boolean `isInEdition` remains false and the code-block meant to be executed 
  on click of the confirm button of alert dialog does not execute as intended.

**Fix:**
- _**Workspace field**_
  The `required` attribute is forcefully set to true for the `folder_id` field so that an empty value for workspace 
   is not considered to be a 'validSelection' and the user faces an alert popup.

- _**Name field**_
  This PR fixes the issue by switching to edit mode whenever user changes the value of a document inspector field.

This PR also adds a testcase in `documents_kanban_tests.js` to ensure that the confirm ('OK') button works as intended.

Task: [3799280](https://www.odoo.com/web#id=3799280&menu_id=4722&cids=2&action=333&active_id=10888&model=project.task&view_type=form)

### Steps to reproduce the issue:

1. Go to _Settings > Technical > Email > Email Templates_
2. Select a template that applies to a Contact
3. Add a mail address in the Cc field
4. Go to _Accounting > Customers > Follow-up Reports_ select one of the reports
5. Click on "Follow up"
6. Select the template with the Cc in the Content Template field
7. The Cc address is not added to the Email Recipients field
8. Click on Send Message in the chatter
9. Open the full view and add the template with the Cc in the Load template field
10. The Cc address is added to the Recipients field

### Explanation:

The field `email_recipient_ids` is not a computed field. Because of it, there is no change called when `template_id` is assigned a new value.

### Suggested fix:

We need to change `email_recipients_ids` according to `template_id` while keeping its current properties (stored, writable).

The method is adapted from `mail.compose.message._compute_partner_ids`.
https://github.com/odoo/odoo/blob/1849b709f1acf0f5546582bf7551129a870e3113/addons/mail/wizard/mail_compose_message.py#L482-L496

opw-3878125

Forward-Port-Of: odoo/enterprise#63918
Forward-Port-Of: odoo/enterprise#61861

With an MX company setup
Create a product with:
- UNSPSC Category: 12352106 Ácidos orgánicos o sus sustitutos
- Hazardous Material Designation Code (MX):
- Hazardous Packaging (MX):
- Tariff Fraction: 2917190800 Ácido fumárico.
- UMT Aduana: kg
- Weight: 1.00

Create a Sale Order with the product
Confirm
Go to Delivery
Set:
- Tansport Type: Federal Highways
- In MX Tab add 'Vehicle Setup' and 'Gross Vehicle Weight'

Validate and Generate Delivery Guide

Error:
Code : CP155 Message : El valor registrado en el atributo "Mercancia:MaterialPeligroso"
no es válido o el valor registrado en el atributo “Mercancias:Mercancia:BienesTransp”
contiene el valor "0" (cero) en la columna "Material peligroso" del catálogo catCartaPorte:c_ClaveProdServCP.

This occurs because the MarierialPeligroso element is not filled
In the ClaveProdServ tab of the CatalogoCartaPorte30 it is specified
if a product or service is (1), not is (0) or may be (0,1) considered hazardous
When having to deal with "may be" hazardous products it is required to set
the 'MaterialPeligroso' element.
Currently, the system does not allow to specify if the "may be" product is
actually hazardous, but if the 'Hazardous Material Designation Code
(MX)' field is not set the MaterialPeligroso element will not be filled,
failing the validation

The proposed workaround is to use the value '0' as flag to indicate
that the maybe hazardous product should not be considered hazardous and
'MaterialPeligroso' will be set to 'No'

opw-3955361
task-3668225

Forward-Port-Of: odoo/enterprise#64153
Forward-Port-Of: odoo/enterprise#63832