This change improves Odoo's internal web test framework so more HTTP-related tests can run directly against the application instead of needing a local web server. It should make automated testing more reliable and easier to maintain, with little direct impact on everyday users.

- add a TestCase which is similar to HttpCase (and copies 75% of it) but uses a `werkzeug.test.Client()` to the WSGI application rather than a `request.Session` to the local server
- duplicate the first file of test_http to validate that this makes sense

TODO:

- should the client be overridden to flush and clear the cache? Probably.
- should the client be extended with a more opener-like API?
  - mostly in terms of the response e.g. Werkzeug 2 provides a `TestResponse` which has a `text` accessor but Werkzeug 1 only has `.data` or `.get_data(text=False)`, same with JSON response
  - but also cookies as a mapping for `authenticate`
  - `werkzeug.test.Client` doesn't support `files=`, instead file-like objects and 2~4-uples are treated as file entries, doesn't seem used tho so maybe we don't care?
- maybe common bits should be extracted from HttpCase? e.g. leave all the xmlrpc and browser parts in HttpCase but extract what deals with the opener and session to a superclass
  - remove `registry_test_mode` flag?

Task 2957347

The web module's automated checks for image URL and embedded iframe fields were moved to Odoo's newer testing framework. This helps maintain product quality and makes future changes easier to validate without affecting day-to-day users.

Convert tests:
* image_url_field
* iframe_wrapper_field

task-3705027

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

Some wording in the setup settings was changed from UK English to US English for consistency. This helps provide clearer, more uniform language for users working with the system.

This fixes words that were in UK english and not US english.

Task: 3866815

The analytic plan view now places the applicability field after the company field, matching the intended form layout. This small usability improvement makes the screen order more logical for users reviewing or editing analytic plans.

Applicability should be the last field in the view. 
Currently, it is company.




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

Unused styling variables were removed from several Odoo interface areas. This reduces maintenance clutter without changing visible behavior for users.

This commit removes assigned but never used SCSS variables.

This update removes style settings that were defined but not actually used across several Odoo Enterprise areas. It helps keep the codebase cleaner and easier to maintain, with no expected change to how users see or use the product.

This commit removes assigned but never used SCSS variables.

Argentine electronic invoicing and VAT reporting now use the shared invoice currency rate stored on accounting entries. This keeps enterprise localization aligned with the main accounting changes and helps ensure consistent currency conversion data across reports and documents.

*: l10n_ar_edi,l10n_ar_reports

In the related community PR the field 'l10n_ar_currency_rate' was removed in favor of the new stored 'currency_rate' field on account.move .
This commit does the necessary changes in enterprise.

task-3634224

see odoo/odoo#147910
see odoo/upgrade#5496