Keep only one form controller patch in Knowledge.

Refine the way the chatter and html form fields are detected for Knowledge
macros:
- Instead of updating the `commandsRecordInfo` at every patch if the record's id
  changed, it can be done as an `onWillUnMount` hook, since we only care about
  the last visited record of the form view.
- Use a `CallbackRecorder` to accurately ask the `Chatter` whether the current
  user is able to send messages or attach files, instead of relying only on the
  presence of the chatter in the `xmlDoc`.
- Add/Move some functions related to registering/discarding/validating a
  `commandsRecordInfo` in the `KnowledgeCommandsService` to limit the amount of
  functions added in the `FormController`.

Use action service to restore the form view instead of clicking on the
breadcrumbs in the DOM. Breadcrumbs are only checked to ensure that the
current view has a breadcrumbs history. This is more robust against future
designs of the breadcrumbs (where not every element of the breadcrumbs list is
displayed directly as a link (some of them can be hidden in a popper).

Add comments to better explain the macro processes and the
`KnowledgeCommandsService`.

Remove usage of `interval` macro property as it is obsolete since [1].

Add a timeout of 10 seconds for macros, to give back control to the user if a
macro is stalled.

Knowledge macros rely on the name attribute of a notebook page to switch
between tabs in a Form notebook. That attribute is not mandatory, so some views
with a valid html_field did not have one. This commit add the name attribute
so those fields can now be manipulated by Knowledge macros.

[1]: https://github.com/odoo/odoo/commit/3a798039d6f200f8e28448ddb6a2d3c46654a203

task-3410128

This error occurs when the next() function has no more items to retrieve from the iterator and we receive an empty `attachments_iter` when calling the next() function.

To produce this error turn on the developer mode and directly open the `sign.template` model `form view` from the `Open View` and click on the save button without entering anything.

see the traceback:
```
StopIteration: null
  File "odoo/http.py", line 2134, in __call__
    response = request._serve_db()
  File "odoo/http.py", line 1710, 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 1737, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "odoo/http.py", line 1938, in dispatch
    result = self.request.registry['ir.http']._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 459, in call_kw
    result = _call_kw_model_create(method, model, args, kwargs)
  File "odoo/api.py", line 439, in _call_kw_model_create
    result = method(recs, *args, **kwargs)
  File "<decorator-gen-235>", line 2, in create
  File "odoo/api.py", line 409, in _model_create_multi
    return create(self, [arg])
  File "home/odoo/src/enterprise/saas-16.4/sign/models/sign_template.py", line 109, in create
    val['attachment_id'] = next(attachments_iter).id
```

To handle this issue we have added a try-except block. using that if we do not get an `attachment_id` or `name`, the record will not be saved.

sentry-4410298400

Forward-Port-Of: odoo/enterprise#46158

If the actual date of an outgoing stock move is out of the mps dates
range, a traceback will appear

To reproduce the issue:
(Need `sale_management`)
1. In Settings:
   - Enable Multi-Step Routes
   - Configure MPS:
     - Range: Daily
     - Number: 7
2. Create a product P
3. Add P in MPS
4. Inventory > Configuration > Rules, edit "Pull from Stock to Custo":
   - Lead Time: 10 days
5. Create and confirm a SO with P:
   - Delivery Date: today + 15 days
6. Open MPS

Error: an Odoo Server Error appears: "IndexError: list index out of
range"

When confirming the SO, a procurement has been created for "today +
15 days". Then, the delivery rule has been used, its lead time has
been applied: the SM is created with a date equal to "today + 5
days", which is inside MPS dates range. As a result, when getting
the outgoing SM for the MPS:
https://github.com/odoo/enterprise/blob/c679d196ac165a8e62aefd2fd5fc69e103c6ebdd/mrp_mps/models/mrp_mps.py#L891-L903
In `_get_moves_and_date` we find the SM and cancel the rule lead
time (so we get the actual expected date): we have a tuple with the
SM and "today + 15 days". But here is the issue: in the while-loop,
we try to find which range index corresponds to that date -> it is
not possible as we are out of dates ranges -> index will be greater
than `len(date_range)` -> `IndexError`

OPW-3372579

Forward-Port-Of: odoo/enterprise#46569
Forward-Port-Of: odoo/enterprise#46293