Original PR description

Description of the issue this commit addresses:

Since the new Tax Returns features in saas-18.3, a method that was used by the method that was generating the xml export of the italian periodic vat report was replaced by one of a different name. The one used by the xml export system has not been modified and therefore tries to call a method that doesn't exist leading to a traceback.

---

Steps to reproduce:

1. Install l10n_it_xml_export.
2. Using an Italian company, go to the montly vat report.
3. Create the closing entry and post it.
4. A traceback shows up.

---

Desired behavior after this commit is merged:

No traceback shows up during the xml export of the italian periodic vat report closing entry posting process.

---

task-4825706

Original PR description

```
* = {account_followup, appointment, approvals, documents, frontdesk, helpdesk, 
hr_contract_salary, hr_payroll, hr_referral, knowledge, l10n_ch_hr_payroll_elm_transmission, 
marketing_automation, mrp_pim, quality, quality_control, room/views, sale_renting, 
sale_subscription, social, spreadsheet_dashboard_sale_subscription, whatsapp}
```

**Current behavior:**
When a field referencing the `res.users` model is included in an XML view, users are offered a "Create" and "Create and Edit" options. If "Create" is selected, it attempts to create the user without required fields like `login`, resulting in a database integrity error due to the NOT NULL constraint on `res_users.login`.

**Improved behavior:**
This commit disables the direct "Create" option for fields referencing `res.users`, preventing invalid record creation.

Sentry - 6263547789

Related Community PR: https://github.com/odoo/odoo/pull/208227

Original PR description

Versions
--------
- 18.0

Fixed in 18.1+ via 752fdb2d2718

Steps
-----
1. Create a quotation;
2. click "Send by Email";
3. schedule the message to get sent at a later time;
4. wait for the message to send, or click "Send Now" in the chatter;
5. refresh the page.

Issue
-----
Quotation state did not get set to `sent`.

Cause
-----
Before this commit, marking the quotation as `sent` happened via a context value. This worked for earlier versions, but with the introduction of scheduled messaging, the context is no longer available when the scheduled message gets sent.

Solution
--------
Add the `mark_so_as_sent` context value to the `notification_parameters` field of `mail.scheduled.message`, and check for this value in the `_post_message` method that gets called when sending the message. If present, re-introduce the context value in the call to `super`.

opw-4794010

Original PR description

### Description of the issue/feature this PR addresses:

- When pasting formatted content (like `<strong>` or `<font>`) into a region that already had same formatting, it caused nested identical tags, leading to exaggerated styling (e.g., "double bold").

```html
<!-- User pastes <strong>text</strong> inside <strong> -->
<p><strong>text []</strong></p>

<!-- Resulting HTML -->
<p><strong>text <strong>text</strong>[]</strong></p>
```

### Desired behavior after PR is merged:

- Prevents unwanted style amplification by unwrapping nested identical formatting tags.

```html
<!-- Resulting HTML -->
<p><strong>text text[]</strong></p>
```

task-4715409

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Original PR description

### Description of the issue/feature this PR addresses:
Prevent sending unnecessary invitation or update emails for events that have already ended by introducing a method to check if an event is over.

### Current behavior before PR:
Event updates/ new syncs with google_calendar might trigger email notifications, even for past events, causing useless invitations/ updated invitations to users.

### Desired behavior after PR is merged:
Email notifications are only sent for active or future events. Creation-from-sync / Updates to past events that have already ended are no longer triggering emails.

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
task-4684432

Original PR description

Previously, the `company_id` field on `budget.analytic` was mandatory.

- Removed the `required=True` constraint on the `company_id` field in the `budget.analytic` model.
- Updated the record rules `budget_comp_rule` and `budget_lines_comp_rule` to allow access to records where `company_id` is either in the user's companies or unset (`False`).

task-4677599

Original PR description

Context:
The Belgian localisation has two Intrastat report handlers:

- Goods: `l10n_be_intrastat.models.account_intrastat_report`
- Services: `l10n_be_intrastat_services.models.account_intrastat_services_report`

`account_intrastat_report.be_intrastat_export_to_xml()` is the single export entry-point for both. It always calls an internal helper named `_be_intrastat_get_xml_file_content(options, results, company)` and then serialises the returned string.

Why it failed:
1. Signature drift The services override expected a fourth positional argument (`date`), so the shared entry-point raised a `TypeError`.

2. Wrong template prefix The helper tried to render `l10n_be_intrastat.intrastat_services_report_export_xml`, but the template is stored under `l10n_be_intrastat_services`, leading to a `ValueError`.

This commit drop the unused `date` parameter and compute the period from options the same way we do in the other function.

opw-4834279