When shapes were extracted to configurator snippets in [1], some configurator-specific snippets were created that do not appear on pages of the specific theme.
Because in [2] the call to `_generate_primary_snippet_templates` is done on a full list of themes instead of only the installed ones, the problem was not noticed: if any theme defines a block, it's website-side configurator-specific template is generated.
This is not the case during an upgrade: the templates are generated only for the installed themes. Because of this some "useless" configurator templates trigger an error when importing their XML definition because their parent template does not exist.

This is fixed in design-themes by adding those templates in a pseudo page `_` in the `configurator_snippets` entry of each theme's manifest. This commit makes sure to not consider that `_` page name as an actual page name.
In master, the templates will be removed instead.

[1]: https://github.com/odoo/design-themes/commit/d206c119720d557c11320ebb3d7339890b8f9efa
[2]: https://github.com/odoo/odoo/commit/928eeca714a161f6bc03343e4dc8af9b050b9841#diff-f49a1e9eda23df9f1d48121ba376a5fabafe70ea18b29d4eab23d737e5d4eeb6R446

Since [1], the colorPalette component is mounted on a new App via the attachComponent compatibility util. The new App is subject to target validation, which fails in mass_mailing and raises a traceback.

This happens because the element for mounting the color palette is created by the top window's document and later attached to the iframe's DOM tree.  Unfortunately this holds true for the entire sidebar is mass_mailing.

Commit [2] apparently added some flexibility to the attachComponent util, temporarily disabling target validation when about to mount an App. But, due to the asynchronous nature of mounting an App, this was not enough for the present case, as the original App.validateTarget function is restored before it gets called when mounting the ColorPalette.

This commit fixes this localized issued, leaving a large-scale fix, in which the snippets menu elements are properly created by the correct document, for a future commit on master. This will have to take into consideration the fact that the code for the snippets menu is shared between mass_mailing and website, and that, in the latter, the snippets menu sits outside the iframe, thus, it is part of the top document tree. Alternatively, the snippets menu should be refactored and converted to owl.

task-3605859

[1]: https://github.com/odoo/odoo/commit/36061a4ab017a463c1d5bf838334cb4c0fac25ee
[2]: https://github.com/odoo/odoo/commit/6a30ab13536a2dc0a8f23df32962cd1ceec71a5d

will get multiple company with multiple currency record as it will try to calculate multiple template
cost currency field value. we need to do iteration for template record then it will resolve the error. Error has been introduced during upgrade.

```
  File "/home/odoo/src/odoo/saas-16.4/addons/product/models/product_template.py", line 189, in _compute_cost_currency_id
    self.cost_currency_id = self.company_id.currency_id or self.env.company.currency_id.id
   File "/home/odoo/src/odoo/saas-16.4/odoo/fields.py", line 1306, in __set__
    self.write(protected_records, value)
   File "/home/odoo/src/odoo/saas-16.4/odoo/fields.py", line 3087, in write
    cache_value = self.convert_to_cache(value, records)
   File "/home/odoo/src/odoo/saas-16.4/odoo/fields.py", line 3010, in convert_to_cache
    raise ValueError("Wrong value for %s: %r" % (self, value))
 ValueError: Wrong value for product.template.cost_currency_id: res.currency(2, 139)
```

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

This traceback occurs when `stock.move.line` record is created with `qty_done`.

To reproduce this issue:

1) Install `mrp_workorder`
2) Create two products `(A, B)`
3) Create a new `bill of material` with component as product `B`
   and product as `A`
4) Add an `operation` and from the `operation` click on `show instruction` button
5) Create a new `quality.point` record with type as `Register Consumed Materials`
6) give `component_id` value as product `B`
7) Now create a new `Manufacturing Order` with the above created `BOM`
8) Conform the record and click on `Open shop Floor`  button from `work order`
9) Click on the `Quality Point` record and click `Continue Consumption` button

Sentry Traceback:-

```
ValueError: Invalid field 'qty_done' on model 'stock.move.line'
  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 "addons/website/models/ir_http.py", line 235, in _dispatch
    response = super()._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 "home/odoo/src/enterprise/17.0/mrp_workorder/models/quality.py", line 351, in action_next
    return self._next()
  File "home/odoo/src/enterprise/17.0/quality_mrp_workorder/models/quality.py", line 38, in _next
    result = super()._next(continue_production=continue_production)
  File "home/odoo/src/enterprise/17.0/mrp_workorder/models/quality.py", line 510, in _next
    line = self.env['stock.move.line'].create(self._create_extra_move_lines())
  File "<decorator-gen-412>", line 2, in create
  File "odoo/api.py", line 415, in _model_create_multi
    return create(self, arg)
  File "home/odoo/src/enterprise/17.0/quality_control/models/stock_move_line.py", line 30, in create
    lines = super().create(vals_list)
  File "<decorator-gen-248>", line 2, in create
  File "odoo/api.py", line 415, in _model_create_multi
    return create(self, arg)
  File "addons/stock_account/models/stock_move_line.py", line 17, in create
    move_lines = super(StockMoveLine, self).create(vals_list)
  File "<decorator-gen-387>", line 2, in create
  File "odoo/api.py", line 415, in _model_create_multi
    return create(self, arg)
  File "addons/mrp/models/stock_move.py", line 43, in create
    res = super(StockMoveLine, self).create(values)
  File "<decorator-gen-225>", line 2, in create
  File "odoo/api.py", line 415, in _model_create_multi
    return create(self, arg)
  File "addons/stock/models/stock_move_line.py", line 305, in create
    mls = super().create(vals_list)
  File "<decorator-gen-12>", line 2, in create
  File "odoo/api.py", line 415, in _model_create_multi
    return create(self, arg)
  File "odoo/models.py", line 4538, in create
    raise ValueError("Invalid field %r on model %r" % (key, self._name))
```

From this PR (https://github.com/odoo/odoo/pull/137864) `qty_done` field is removed from `stock.move.line` model.

When a record is being created with the `qty_done` field a traceback occurs.

 After applying this commit will resolve the issue by replacing `qty_done` with
`quantity` field.

sentry-4636904734

Steps to reproduce:

  - Install appointment module
  - Go to Calendar -> Configuration -> Appointment Invitations
  - Create a new Appointment Invitations and add a slot with: From: 12/XX/XXXX 10:10:00 To: 12/XX/XXXX 12:12:00
  - Save and go to preview
  - Click on the slot

Issue:

  The page does not exist (404 as request status).

Cause:

  When generating the link for each slot, the duration is added as
  floats in the URL (and therefore might have a number with more than
  2 decimals, which is our case).
  When accessing the URL, the duration is used to match the slots with
  same duration, however, the duration field on slots are rounded to 2
  decimals.

  https://github.com/odoo/enterprise/blob/c5cff900d8abdf6f469c6355cc6c745b0e8a3043/appointment/models/calendar_appointment_slot.py#L45

Solution:

  Round the duration to 2 decimals when comparing the URL duration param
  with slot duration field values.

opw-3384499

Forward-Port-Of: odoo/enterprise#51889
Forward-Port-Of: odoo/enterprise#47311

### Current behavior:
The knowledge page's tree fails to load on the client's database, making the knowledge app unusable.

### Expected behavior:
The tree loads correctly, allowing users to create and navigate knowledge articles.

### Steps to reproduce:
- Create a large number of articles in the knowledge section.
- Include multiple base64-encoded images in the body of these articles.
- After some time, the tree fails to load, throwing a memory error.

### Reason for the problem:
During tree construction, the ORM retrieves visible articles without pagination, which can create an excessive memory usage. The default prefetching loads all fields, including the body field, which can be large like in this case (1.2Gb).

We can see that in memray, the cache is at 1.6Gb when the tree is fetched:
![2023-11-22_16-30](https://github.com/odoo/enterprise/assets/136497220/d96e8878-63a2-4d7f-82b7-0af4e2361631)

### Fix:
Remove the prefetching of the body field in knowledge.article. This optimization speeds up the query and eliminates the possible memory error with a lot of large body.

### Reference:
opw-3572719

Forward-Port-Of: odoo/enterprise#51786
Forward-Port-Of: odoo/enterprise#51340