This update enhances the stability of our IoT Box integration by splitting websocket messages. Previously, messages targeted multiple IoT devices simultaneously, which could cause issues. Now, each message is sent individually, per device, ensuring smoother and more reliable communication.

In order to ensure ws compatibility with stable IoT Boxes versions, we now split websocket messages to send one per IoT identifier, instead of one targeting multiple ones.

related: odoo/odoo#234175

Forward-Port-Of: odoo/enterprise#100317
Forward-Port-Of: odoo/enterprise#100127

This update enhances the documentation for Odoo's resource and shared method usage within the html_builder and html_editor modules. The changes improve type definitions, ensuring better code clarity and maintainability, which supports future development and reduces potential errors.

backport of https://github.com/odoo/odoo/pull/236084

This update allows IoT devices to connect to the Odoo POS system without requiring a secure HTTPS certificate. It leverages a new feature in Chromium (142) that supports HTTP requests over the local network (LNA). This simplifies the setup and improves compatibility for IoT devices.

Enterprise PR: https://github.com/odoo/enterprise/pull/100331

**This PR contains 2 commits:**

- **[IMP] iot_base: allow use of LNA for IoT requests**
Chromium 142 added support for HTTPS -> HTTP requests on the local network (Local Network Access). This commit adds a flag to the IoT longpolling class to enable LNA support. The flag forces all requests to use HTTP even in an HTTPS environment. It also sets the `targetAddressSpace` option to `local` in the `fetch` request.

- **[IMP] point_of_sale: use_lna support for IoT requests**
Since https://github.com/odoo/odoo/pull/235702, there is a `point_of_sale.use_lna` system parameter. When it is set, ePOS requests will use HTTP instead of HTTPS, and the `targetAddressSpace: "local"` option is used in the `fetch` request. This bypasses the need for a HTTPS certificate.

This commit adds the same functionality to all IoT requests from the POS. This should allow the IoT box to function correctly without a HTTPS certificate.

task-5353672

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

Forward-Port-Of: odoo/odoo#237147

This update enables IoT devices to function without requiring HTTPS certificates by utilizing a new system parameter. It also displays a warning message when HTTP requests to the Blackbox fail, ensuring a smoother user experience. This change supports the recent odoo/odoo#235702 update.

Community PR: https://github.com/odoo/odoo/pull/237147

Since odoo/odoo#235702, there is a `point_of_sale.use_lna` system parameter. When it is set, ePOS requests will use HTTP instead of HTTPS, and the `targetAddressSpace: "local"` option is used in the `fetch` request. This bypasses the need for a HTTPS certificate.

This commit adds the same functionality to all IoT requests from the POS. This should allow the IoT box to function correctly without a HTTPS certificate.

In addition, we now show a warning message when a request to the Blackbox via HTTP fails and has to fallback to the websocket.

task-5353672

Forward-Port-Of: odoo/enterprise#100331