This update corrects how Italian e-invoicing test attachments are stored so they work with newer Python validation rules. It helps keep automated testing reliable and reduces the risk of false failures during maintenance or upgrades.

This commit fixes an error when running the `test_edi_import` test on Python 3.14, which is stricter about base64 validation.

Ultimately, the root issue was that raw test content was being passed to the `datas` field of an attachment when a base64 representation was actually expected (which is obviously invalid base64). Passing it via the `raw` field instead correctly handles the raw binary data.

runbot-939133

Forward-Port-Of: odoo/odoo#266731

Removing a background image in the website editor now also clears its color or gradient overlay. This prevents leftover styling from remaining on page sections, keeping edited website content visually clean and predictable.

Steps to reproduce:
- Edit a website page.
- Select a section with a background image.
- Set a gradient color filter on the background image.
- Remove the background image.
=> The gradient color filter stays in the section DOM.

After this commit, `removeBackgroundImage` directly removes the
related `.o_we_bg_filter`.

Forward-Port-Of: odoo/odoo#265025

This change makes an automated website test more stable by removing timing uncertainty that could occasionally cause false failures. It helps keep validation runs dependable without changing any customer-facing behavior.

This commit fixes the test "waitForTimeout does not trigger update if
interaction is not ready yet", which could very rarely fail on runbot.

**Origin of the problem**
The test relies on precise timings, but the helper `advanceTime` could
introduce a non-deterministic lag because, when called with default
options, it awaits for an animation frame. If the lag happens to be too
long, the second `verifySteps` is called too late and the test fails.

**Fix**
The helper `advanceTime` is now called with the option `animationFrame`
set to false to avoid awaiting for an animation frame. For additional
safety, the waiting time is also reduced.
Two changes not directly related to this problem have been applied to
improve the test: 1. an unnecessary `await` in `willStart` has been
removed; 2. the `animationFrame` has been set to false also on the
second `advanceTime` (a non-deterministic lag here can't fail the test,
but still there is no reason to await for the animation frame).

runbot-243515

Forward-Port-Of: odoo/odoo#266432

This pull request addresses a preliminary fix (POC) for inconsistencies in account reporting across various Odoo localization modules (e.g., France, Germany, Spain). The changes involve updating XML data files and models to improve the accuracy and consistency of financial reports. This ensures that reports generated for different regions align with local accounting standards.

wip

This update optimizes the way Odoo calculates the styles for work orders, resulting in faster performance during common actions like resizing windows or scrolling through large tables. By using a more targeted approach, the system avoids unnecessary style recalculations, leading to a smoother user experience.

Avoid using the :has() selector and use a specific class on the body instead to replicate the same behavior, this reduces work during the "Recalculate Style" phase.

It lowers recalculation time during window resizes, heavy scrolling, and table sorting by preventing broad selector matches and limiting style checks to elements with the specific class.

This update fixes a minor issue in the DMFA report where the 'Calculation Basis' and 'Contribution Type' headers were incorrectly switched. The headers have now been corrected to their proper order, ensuring accurate reporting of payroll data for Belgian businesses using this module. This ensures data consistency and reliability.

DMFA report had "Calculation Basis" and "Contribution Type" header switched. Got switched back correctly.

task-6227590