**Steps to reproduce:**
1. Install `l10n_de_reports` module.
2. Configure a company with a valid SteuerNummer.
3. Post some vendor bills with `19% I` VAT.
4. Go to *Accounting → Reporting → Tax Report*.
5. Export the report to XML from gear icon.

**Observed behavior:**
- The generated XML contains amounts with a comma `,` as the decimal separator.
- Elster ignores values with commas, so amounts are missing from the submitted VAT return.

**Root cause:**
- The QWeb XML export replaced the decimal point `.` with a comma `,`.
- Elster launched a new tax return application (*einfachELSTERplus*), which enforces `.` as the decimal separator.

**Solution:**
- Stop replacing `.` with `,` when exporting values to XML.
- Keep amounts as floats with period separators, while still rounding or inverting values as required for specific Kz fields.

**ref:**
https://www.elster.de/eportal/helpGlobal?themaGlobal=osseust_import

opw-4935738

Forward-Port-Of: odoo/enterprise#94130
Forward-Port-Of: odoo/enterprise#93623

Steps to reproduce
===================
1. Insert any list view in the knowledge article.
2. Click on open view from the article.
3. Come back and click edit.
-> Traceback occurs

Technical
=============
When we open a view from an embedded view in the article, we add `orderBy` from the
action context to the action props if it exists. As the action prop is initialized
and assigned directly from `embeddedState.additionalViewProps` without copying, it
mutates the original object, changing the `data-embedded-props` attribute in the DOM
and marking the body of the article as unsaved from `StateManager.changeState`. The
action continues, and the action service commits those unsaved changes to the article.

Once it is saved and the action is executed, when we get back to the article and
click on edit, we check for `additionalViewProps` to be undefined/empty for all
other views except calendar. As the DOM already has saved data in attributes, we
get `orderBy` in `additionalViewProps`, and thus a manual error is thrown in the
`editView` function.

After this commit
===============
Clone `additionalViewProps` when preparing the view action props.

Task-4921282

Forward-Port-Of: odoo/enterprise#91113

### [PERF] l10n_pe_edi: Avoid OOM during installation

### Description:

Installing `l10n_pe_edi` on large databases with many moves and move lines could cause out-of-memory (OOM) errors. This happens because several stored fields need to be computed at installation.

### Fix:

This fix adds the columns via SQL, preventing Odoo from computing and populating the field for all existing records. This reduces memory usage and avoids installation failures.
____
### [FIX] l10n_pe_edi: Fix error during post-init hook

### Description:

During installation, the `l10n_pe_edi` module's post-init hook attempts to update tax groups, setting the new `l10n_pe_edi_code` field. This can cause an error if a tax group doesn't exist and needs to be created, because the name field is missing in the list of values given to the `_load_records` function.

### Fix:

This fix filters the tax groups to only update existing ones. This prevents `_load_records` from trying to create new groups, which avoids the installation error.

___
### Reference:

opw-4982181

Forward-Port-Of: odoo/enterprise#91997

Issue:

* When a sign request was copied via a public share link, the process failed 
  with an `AccessError`.
* This happened because the computed field `cc_partner_ids` (partners in CC) was
  read as the *Public user*, who does not have read rights on `res.partner`.
* With recent core changes, many2many writes now enforce read access on linked
  records, making the error unavoidable.

Steps to reproduce:

1. Open the master on Runbot.
2. Upload a PDF to Sign.
3. Press the `Share` button.
4. Log out of the account.
5. Open the copied share link.
6. A traceback appears in the log with an access error on `res.partner`.

Fix:

* Compute the `cc_partner_ids` under `sudo()` in the copy.
* This ensures the system can read the CC partners with elevated rights and only
  passes their IDs (safe to use) to `message_subscribe`.

Impact:

* Public users can now open and copy sign requests from share links without
  triggering access errors.
* Preserves security: only the system uses `sudo()` for computing, while the
  actual subscription still writes the partner IDs as normal.

task- 4067945

---

```yml
During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/odoo/odoo/community/odoo/http.py", line 2740, in __call__
    response = request._serve_db()
  File "/home/odoo/odoo/community/odoo/http.py", line 2281, in _serve_db
    raise self._update_served_exception(exc)
  File "/home/odoo/odoo/community/odoo/http.py", line 2279, in _serve_db
    return service_model.retrying(serve_func, env=self.env)
  File "/home/odoo/odoo/community/odoo/service/model.py", line 184, in retrying
    result = func()
  File "/home/odoo/odoo/community/odoo/http.py", line 2326, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "/home/odoo/odoo/community/odoo/http.py", line 2541, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
  File "/home/odoo/odoo/community/odoo/addons/base/models/ir_http.py", line 357, in _dispatch
    result = endpoint(**request.params)
  File "/home/odoo/odoo/community/odoo/http.py", line 788, in route_wrapper
    result = endpoint(self, *args, **params_ok)
  File "/home/odoo/odoo/enterprise/sign/controllers/main.py", line 498, in make_public_user
    new_sign_request = sign_request.with_user(sign_request.create_uid).with_context(no_sign_mail=True, sign_request=sign_request).copy({
  File "/home/odoo/odoo/enterprise/sign/models/sign_request.py", line 243, in copy
    new_request.message_subscribe(partner_ids=old_request.with_user(old_request.create_uid).cc_partner_ids.ids)
  File "/home/odoo/odoo/community/odoo/orm/fields_relational.py", line 45, in __get__
    return super().__get__(records, owner)
  File "/home/odoo/odoo/community/odoo/orm/fields.py", line 1738, in __get__
    self.compute_value(record)
  File "/home/odoo/odoo/community/odoo/orm/fields.py", line 1904, in compute_value
    records._compute_field_value(self)
  File "/home/odoo/odoo/community/addons/mail/models/mail_thread.py", line 468, in _compute_field_value
    return super()._compute_field_value(field)
  File "/home/odoo/odoo/community/odoo/orm/models.py", line 4913, in _compute_field_value
    determine(field.compute, self)
  File "/home/odoo/odoo/community/odoo/orm/fields.py", line 81, in determine
    return needle(*args)
  File "/home/odoo/odoo/enterprise/sign/models/sign_request.py", line 157, in _compute_cc_partners
    sign_request.cc_partner_ids = sign_request.message_follower_ids.partner_id - sign_request.request_item_ids.partner_id
  File "/home/odoo/odoo/community/odoo/orm/fields.py", line 1812, in __set__
    self.write(protected_records, value)
  File "/home/odoo/odoo/community/odoo/orm/fields_relational.py", line 727, in write
    self.write_batch([(records, value)])
  File "/home/odoo/odoo/community/odoo/orm/fields_relational.py", line 748, in write_batch
    self.write_real(records_commands_list, create)
  File "/home/odoo/odoo/community/odoo/orm/fields_relational.py", line 1475, in write_real
    raise AccessError(model.env._("Failed to write field %s", self) + "\n" + str(e))
odoo.exceptions.AccessError: Failed to write field sign.request.cc_partner_ids
Uh-oh! Looks like you have stumbled upon some top-secret records.

Sorry, Public user (id=3) doesn't have 'read' access to:
- Contact (res.partner)

If you really, really need access, perhaps you can win over your friendly administrator with a batch of freshly baked cookies.
```