Ecuador electronic documents can now include a product auxiliary code on invoices and credit notes. This helps businesses meet local electronic invoicing requirements and makes the code visible on invoice reports.

- Add a new field to the product template for the auxiliary code required for electronic documents

Adds options in the Barcode app to hide the expected quantity during inventory counts and require counting all products in a scanned location. This helps businesses get more accurate physical inventory results by reducing shortcut counting and lowering the risk of missed items, while also fixing scrolling for grouped barcode lines.

Creating a spreadsheet in Documents will no longer show a template selection dialog when no templates are available. This restores the previous behavior, reducing unnecessary steps for users who just want to create an empty spreadsheet.

This reverts commit 6d0af6cf42dbf033fe2b886d8ba60daec611f104.

Task: 3761476

This update streamlines accounting-related test preparation so tests create fewer unnecessary default records, such as extra currencies and companies. It helps keep internal validation faster, simpler, and easier to maintain without changing day-to-day product behavior.

Removal of chart_template_ref and other arguments of setUpClass
Avoid second currency and company created by default
For currencies setup in test, avoid the data object

Also removed the Test class `TestSaleTimesheetEnterpriseMultiCompany` as it is not used

Point of Sale users now use one input field for customer contact details instead of separate fields for WhatsApp and email. The available send options for SMS, WhatsApp, and email are highlighted automatically based on what the user enters, making receipt sharing clearer and faster.

Before this commit:
===================
There were two separate input boxes for WhatsApp and email, each functioning
differently.

After this commit:
===================
With this commit, a single input box is implemented to handle all communication
channels, including SMS, WhatsApp, and email. Buttons will now dynamically
highlight and activate based on the input value.

task- 3411407

Document-related screens now allow long titles to wrap onto multiple lines instead of being cut off or forced into one line. This makes longer folder, rule, and facet names easier for users to review without losing context.

Earlier the title was stuck to the single line in various models of the documents. This PR addresses the issue and provides multiline support for the titles.

Task-3870149

Users can now collapse the Documents inspector panel to free up more space for viewing and previewing documents. The collapsed panel keeps quick access to reopening the inspector and opening the chatter, improving usability without removing key actions.

This PR adds the possibility of collapsing the documents inspector panel in order to have more space to view and preview documents.

It adds a `toggle button`  to the documents inspector. In the uncollapsed form of  inspector, this button allows to 'fold' the inspector. While in the collapsed inspector form, the toggle button allows to 'unfold' the inspector sidebar.

Apart from the 'unfold' button, the collapsed sidebar contains the 'open chatter' button, which works similarly as it does in the uncollapsed form of inspector.

**Technical:**
The boolean `isFolded` is introduced to manage the folded/unfolded state of the documents inspector. 
On the basis of this boolean, all the inspector sections are displayed as follows:

_**`isFolded` is 'True' i.e. the inspector is collapsed:**_
- - It applies the sidebar width and displays only toggle and chatter buttons.
  `d-flex` class is added to sidebar and margin is added to chatter button to ensure the buttons are aligned properly.
- Does not display documents preview and info sections.
- Applies the title 'Unfold' to the toggle button and changes its icon to indicate the same.

_**`isFolded` is 'False' i.e. the inspector is uncollapsed:**_
- It applies the documents inspector width and displays all inspector buttons.
- It now displays both the documents preview, and info sections.
- Applies the title 'Fold' to the toggle button and changes its icon to indicate the same.

This PR adds a margin to both, toggle and chatter buttons, to ensure that there is an appropriate gap between the buttons in the uncollpased form of the inspector.

Task: [3741366](https://www.odoo.com/web#id=3741366&menu_id=4722&cids=2&action=333&active_id=965&model=project.task&view_type=form)

A helpful tooltip has been added to the Prorata Date field in the Asset Management module to guide users on how to use this feature. This enhancement improves the user experience by providing clearer instructions directly within the application, reducing confusion and support requests.

[ADD] account_asset: Add tooltip to Prorata Date

Add tooltip to Prorata Date field in account_asset module and add its translation

Reason: Enhance user-experience

Task-3864117

This update improves how double holiday pay recovery is calculated in the Belgian payroll system to ensure compliance with legal requirements. The change affects how employees' double holiday compensation is computed, ensuring accurate and legally compliant payroll processing for Belgian operations.

This will fix the computation of the double holiday pay recovery to match legal requirements.

Task: 3893867

This update removes unnecessary duplicate requests to Google Calendar when synchronizing appointments. The system now reuses information returned from Google during the initial sync instead of making additional requests, resulting in faster synchronization and reduced API calls. Google Meet URLs continue to be added to appointments correctly with this more efficient approach.

This commit removes the write override of calendar.event records, since this override
was doing unnecessary requests on Google side when synchronizing again events that were
just synchronized.

After this commit, the function get_post_sync_values() will reuse the values returned by
the insertion in Google and write in the event right away, saving requests to Google. The
objective of the previous write override was to write the google meet URL in the event,
and now this is still being done correctly by means of the new strategy.

related-to: https://github.com/odoo/odoo/pull/163364
task-389382

The quiz feature in website slides now uses green to highlight correct answers instead of purple, making it much easier for learners to quickly distinguish between correct and incorrect responses. This improves the user experience by providing clearer visual feedback during quiz interactions.

Currently, if we select the correct answer for a quiz question, `primary theme color(purple)` is applied to the `fa-check` icon. 
Hence, it is difficult to distinguish between the correct and incorrect answers.

This PR changes the color applied to the `fa-check` icon in case a correct answer is selected, from `primary theme color(purple)` to `success theme color(green)`.

Task-[3884674](https://www.odoo.com/web#id=3884674&menu_id=4722&cids=2&action=333&active_id=965&model=project.task&view_type=form)

This update improves how Google Calendar events are created and synchronized. When events are added to Google Calendar, the system now captures and saves important information (like meeting URLs) immediately after creation, rather than discarding it. This reduces the need for additional updates later and makes the synchronization process more efficient.

Before this commit, when inserting an event in Google side, we were throwing away the insertion values returned by Google and keeping only the event id. This was not a good practice because we could already write important values such as meeting URL and then spare future write calls. Additionaly, when writing values from google, we were sending through the context the 'write_dates' key, that would only be used once but would be kept in the context (when it is not needed).

After this commit, a callback function was added to write the event information right after the 'insert' function is executed, alongside of a function to get the desired post sync values describing which fields will be written in the event. Thus, we can write in the event right away after its creation. Since we are in a stable branch, this strategy was the only option to avoid changing the 'insert' function return and, by consequence possibly breaking custom code. In addition, now we delete the recently used 'write_dates' context key from the context in order to prevent future misuse of it.

task-3893827