The IoT module now loads the websocket connection information during the initial page load instead of making a separate request each time a view opens. This improves performance by reducing unnecessary network calls and provides a faster, smoother user experience when working with IoT devices.

`IoTWebsocketService` was making an RPC call every time the view loaded.  
Now, we load it in the session_info to provide it to the view while rendering html.

Task: 4037030

This update removes unnecessary action buttons that opened journal items from the GST Return Period report sections. By eliminating these extra actions, the GST return reporting process is now more focused and efficient, reducing clutter and helping users concentrate on the essential information they need.

With this PR, the actions to open all journal items have been removed from all GSTR sections of the GST return Period.

This change helps streamline the GST Return by eliminating unnecessary actions, ensuring a more focused and efficient reporting process.

**task**-3908555

This update improves how GST tax reports handle point of sale transactions in India by automatically setting the Place of Supply information on general journals when it's missing. The changes also fix issues with missing point of sale details in GST return reports, ensuring more accurate tax compliance reporting for Indian businesses.

In this PR:
- Set Place of Supply on 'general' journals with POS sessions if a country is
India and Place of Supply are not set.
- Adjusted state ID computation for account moves with POS sessions.
- Fixed handling of missing POS line details in GST return period report.


Task ID: 3935317

This update corrects how service accounts and export accounts are categorized in Chile's F29 tax report. The fix ensures services are properly included in the VAT base calculation and exports are correctly mapped to the exempt base, improving the accuracy of tax reporting for Chilean businesses.

vat base and change exempt base to exports account.

Fixed an issue in the Barcode app where scanning GS1 barcodes containing both packaging information and weight was calculating incorrect quantities. When a product uses Units as its measurement, the weight information is now properly ignored and only the packaging quantity is used, preventing incorrect multiplication of quantities.

Issue
=====

When a GS1 barcode contains both a packaging and a weight, the quantity is wrong because we use the weight as the quantity and multiply it by the packaging quantity.

How to reproduce
================

- Enable "Product Packagings" and "Units of Measure";
- Select GS1 nomenclature as the Barcode Nomenclature;
- Create a product with a packaging for multiple quantity (e.g.: 4 Units) and with a valid GTIN (e.g.: 12345600012349);
- In the Barcode app, create a new receipt;
- Scan a GS1 barcode containing both the packaging barcode and a weight (e.g.: 10123456000123493103001500) => The scanned weight is used as the quantity and is multiplied by the packaging quantity (in this example, the quantity will be 6, because 4 units x 1.5 kg = 6 units)

Expected Behavior
=================

Since the associated product uses Units as UoM, the scanned weight can't be converted into quantity (we can't convert g or kg into units), so this information should be ignored and the packaging quantity should be used alone instead.

Note that the packaging quantity will still multiply the scanned quantity if the share the same UoM category. This behavior is still supported to be able to scan multiple packagings at once. That said, this use case make sense for products using Units only.

[OPW-3988826](https://www.odoo.com/odoo/11258/tasks/3988826?cids=1)

Forward-Port-Of: odoo/enterprise#65073

This update removes action buttons that were incorrectly appearing on grouped summary lines in financial reports. When reports use prefix grouping to organize data, buttons now only appear on actual data lines where they can perform meaningful actions, preventing errors or unintended record creation when users click buttons on group headers.

*l10n_account_customer_statements,l10n_my_reports,l10n_us_reports

Currently some reports add buttons on their lines to perform some action on them. However, when prefix groups are used, the buttons are also shown on these lines, but refer to nothing and will thus either cause an error when clicked or lead to a new record.

This commit fixes that by providing a generic hook in the `line_name` template to inject buttons. This generic hook checks whether the line is a prefix group line and doesn't render the buttons if it is.

All other reports were adapted to use this hook now.

task-3932945

Fixed an issue where sample values in the WhatsApp Composer were not updating when users changed the WhatsApp template. Previously, the composer would display sample values from the initially selected template instead of reflecting the newly chosen template. This fix ensures that sample values now correctly update whenever a different template is selected, improving the user experience when composing WhatsApp messages.

## Before this PR
In WhatsApp Composer, the Sample Values do not update when changing the WhatsApp Template. Instead, it display the sample values from the initially selected template.

## After this PR
The Sample Values will now update according to the selected WhatsApp Template.

Task-3996935