The SEPA payments module no longer includes QR code payment functionality, which is being handled separately in a more reusable way. This makes the payment features cleaner to maintain while keeping SEPA transfers focused on their core purpose.

This is part of the QR-code refactoring done in community. account_sepa module now does not contain anything related to SEPA QR-codes anymore, as they are a distinct feature.

This change updates an internal Web Studio report editor test to match the latest image selection behavior. It helps keep automated checks reliable after the media dialog now selects images immediately in single-image mode.

In odoo/odoo#45174 the media-dialog behaviour was changed so that an
image is selected immediately when it is clicked and the dialog is not
in 'multi-image mode', as such, a test had to be adapted so that it no
longer tries to click that button. Additionally, the test tries to click
the first attachment using domUtils.click, which checks for visibility,
but that same PR makes it so that attachments are not displayed until
their image is loaded, so we also have to remove the d-none class before
trying to click.

task-2091417

This fix ensures that when certain add-ons are uninstalled, records using options added by those add-ons are cleaned up safely. It reduces the risk of uninstall errors or leftover data across shipping providers, payments, payroll, check printing, marketing SMS, and VoIP-related modules.

This change updates how search panel range selection is called so it stays aligned with the latest platform behavior. It is a minor internal adjustment that helps keep related views and filters working consistently without changing day-to-day business workflows.

Steps to reproduce the bug: - Let's consider a begian company C - Let's consider a french customer P with a VAT number - Let's consider a product PR with 100€ as sales price - Create a customer invoice I1 with P and 0% EU M as tax and valid it - Create a customer invoice I2 with P and 0% EU T as tax and valid it - Go to Partner VAT Intra Bug: Code T and inta code 46T were used for I1 instead of L and 46L No code no intra code were used for I2 instead of T and 46T opw:2224381 F

Steps to reproduce the bug:

- Let's consider a begian company C
- Let's consider a french customer P with a VAT number
- Let's consider a product PR with 100€ as sales price
- Create a customer invoice I1 with P and 0% EU M as tax and valid it
- Create a customer invoice I2 with P and 0% EU T as tax and valid it
- Go to Partner VAT Intra

Bug:

Code T and inta code 46T were used for I1 instead of L and 46L
No code no intra code were used for I2 instead of T and 46T

opw:2224381

Forward-Port-Of: odoo/enterprise#9545