Odoo Release Updates

This commit fixes a test flakiness issue in the livechat module where test results varied depending on whether the optional rating module was installed. The fix dynamically filters message fields based on installed modules rather than expecting a fixed set of fields, ensuring consistent test behavior across different Odoo installations.

[FIX] im_livechat: fix runbot issue due to remove livechat-rating relation

This commit refactors the bus notification assertion system in Odoo tests by introducing a unified BusResult descriptor class to replace the previous two-list approach (channels and messages). The new system provides clearer test semantics, prevents stale data from affecting assertions, compares dictionaries regardless of key order to eliminate brittle failures, and delivers explicit error messages showing expected versus actual notifications. This improvement strengthens test reliability across mail, calendar, livechat, and other modules while making test code more readable and maintainable.

[REF] bus, mail, *: improve assertion on bus notifications

This commit fixes a critical traceback that occurred when internal users started live chat conversations with the hr_holidays module installed. The root cause was unsafe access to user.activeCompany in the employee_id computed field, which is not available in the frontend session. The fix adds optional chaining (?.) to guard against undefined activeCompany, reorganizes asset bundles for better modularity, and adds comprehensive test coverage including a new shared embed test that validates the scenario works with HR employee records present.

[FIX] hr, *: prevent traceback when starting live chat as internal user

This commit applies a systematic OWL3 migration across the entire Odoo codebase by prefixing all template variable references with "this." to comply with upcoming OWL3 requirements. In OWL3, component instance properties must be explicitly accessed via "this." in templates, changing from implicit scope resolution to explicit context binding. This large-scale automated refactoring affects template files across multiple modules including account, board, CRM, HR, and many others, converting patterns like "showUploadButton" to "this.showUploadButton" and "state.name" to "this.state.name" throughout XML templates.

[IMP] *: run rendering context migration script entire codebase

This commit fixes a failing livechat digest test in the runbot environment by removing any existing livechat channels before test execution. The test was failing because demo data created additional livechat channels that interfered with the digest calculations, so the fix ensures a clean slate by deleting all livechat channels prior to running the test setup.

[FIX] im_livechat: fix runbot livechat digest test

This commit enhances the Live Chat user experience through four targeted improvements: rating filters are now grouped under a collapsible "Rating" section for cleaner interface organization, the sessions pivot view axis has been flipped for better data visualization, empty state messaging has been rewritten to be more instructive and action-oriented, and the Chatbot "Channels" button now intelligently opens the form view directly when only one channel exists instead of always showing a list view. Additionally, technical menu items have been reorganized under the main Technical menu structure.

[IMP] im_livechat: improve Live Chat views

This commit fixes multiple printing issues in the Discuss app by hiding non-essential UI elements during print and ensuring proper layout overflow visibility. The sidebar, message composer, thread actions, and visitor offline banners are now hidden when printing, while a new print stylesheet ensures the discuss container displays correctly, similar to existing knowledge module print behavior.

[IMP] im_livechat, mail: enhance print layout in discuss

This fix corrects a bug in im_livechat where the livechat channel name was incorrectly duplicated when an agent initiated a self-chat (talking to themselves). The issue occurred because the visitor_user variable was being set even when the visitor and agent were the same person, causing the agent's name to appear twice in the channel name. The fix prevents visitor_user from being assigned when the current user equals the agent, ensuring the channel displays with a single name instead of duplicated entries.

[FIX] im_livechat: duplicated name in self livechat