Odoo Release Updates

This change removes the "Uploading..." text that appeared during file attachment uploads in the mail chatter by setting the showUploadingText property to false on the FileUploader component. The removal is justified because an upload progress indicator already exists within the attachment box itself, making the redundant text unnecessary and improving the user interface clarity.

[IMP] mail: remove "Uploading..." text

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 consolidates avatar card handling across HR modules by centralizing the single source of truth for employee information in hr.employee records rather than duplicating data across multiple models. The hr.employee.public model is now simplified to act as a proxy to hr.employee using access control, eliminating duplicate field definitions and complex JavaScript patches. The store service's employee chat lookup is refactored to use the standard Store API instead of maintaining a separate employee cache, improving consistency and reducing code complexity.

[REF] mail, *: clean up avatar card and related models

Fixed a traceback that occurred when users selected channel mentions from the @ suggestion list in the mail composer. The issue arose from incomplete code migration where the `channel` attribute was renamed to `thread` in a previous commit, but the suggestion template still referenced the old attribute name. The fix restores the `channel` property in the suggestion object while keeping the renamed `thread` property, and corrects the template reference to use the appropriate channel suggestion template. A comprehensive test tour was added to verify the channel mention selection flow works correctly.

[FIX] mail: fix traceback when selecting items from @ mention in composer

This fix prevents unwanted formatting and styles from being pasted into the HTML editor composer in Odoo's Discuss module. The change intercepts paste events, sanitizes the HTML content, and strips out disallowed tags and styles, allowing only a controlled set of formatting tags (bold, italic, lists, links, etc.) while preserving essential mail-specific class names for mentions and redirects. This ensures consistent message formatting and prevents users from inadvertently introducing problematic HTML or styling into their composed messages.

[FIX] mail,*: no formatting paste in HTML composer

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 the messaging menu counter calculation when the Discuss app is not actively in use by ensuring archived channels and muted channels are excluded from the unread message estimation. The issue occurred because the server-side counter estimation included channel members from archived and muted channels that were not actually displayed in the UI, causing the counter to be inflated. The fix adds filters to check both channel.active status and mute_until_dt field in two locations where the counter is calculated.

[FIX] mail: correct messaging menu counter when not using Discuss

This commit integrates user activity management directly into the attendee calendar view by displaying pending activities as special all-day events that users can interact with via a popover interface. Users can toggle activity visibility through a calendar sidebar filter, reschedule activities to specific dates, and access related records, with the feature designed to be optional and controlled through user settings. The change also refactors activity field storage to include res_name for linking and removes obsolete calendar event ordering logic that was specific to work locations.

[IMP] mail,calendar: add activities in attendee calendar