The mail app now centralizes how messages are prepared and sent, reducing duplicated logic across the message composer. This should make message sending more consistent and easier to maintain without changing the user workflow.

The code that is used to sent message is splitted between composer and
composer_view model.
This PR centralize the sending process inside a message_composition model.

The body of a message is voluntarily NOT a compute to avoid possible performances
issues.

Part of task-2390637

This update improves how Odoo records chat channel membership and message-seen information. It should make mail and messaging activity more efficient and reliable without changing the day-to-day user experience.

Updates how message read and fetched status changes are handled in the Mail app. This makes notification processing more consistent and helps keep conversation status information reliable for users.

Mail message status indicators such as history, required action, and starred are now calculated automatically instead of being stored separately. This improves consistency in conversations and notifications, reducing the chance of outdated message states appearing to users.

The web interface documentation now clearly states the four supported placement choices for popovers. This helps teams configure interface elements more consistently and reduces confusion during development or customization.

Position option has only 4 possibles values.

The accounting module no longer stores a separate off-balance marker on accounts because the same information is already available through the account type. This reduces duplication and helps keep accounting configuration and related processes more consistent without changing core business workflows.

We don't need the `is_off_balance` field on `account.account` as the same thing can be checked with `account_type`.





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

This update improves the JavaScript development tools used by Odoo teams and prepares them for automated lint checks in runbot. It should make code quality checks easier to run consistently while improving developer productivity and editor support.

## Summary

- Use of jsconfig instead of tsconfig
- jsconfig deployed with tooling, no need for CLI
- ecmascript bumped to version es2022 (static properties)
- prettierrc merged inside the eslintrc
- add a few globals
- cleanup package.json scripts
- add script to lint/format only the diff (opposed to staged files)
- bump up node packages versions
- use eslint as cli instead of prettier-eslint, as eslint does provide
parsable output for runbot.
- add the typescrit types of libs as dependencies + main.d.ts to
improve autompletion.

This upgrade makes it easier to deploy and use the js tooling, as it is
expected more and more people will use it if a lint check is added to
the runbot.

## About the runbot:
The commit gets the code ready to enable the lint on the runbot.
It will lint the code with the same rules and same ignore file.
The only difference is the runbot will check only the diff and not the
entire commited file.
The goal will be to progressively (and aggressively) whitelist modules
to converge to a nice formatted codebase.
The runbot could run a command such as
`echo '{\"extends\": [\"plugin:diff/diff\"]}' | eslint --resolve-plugins-relative-to . -c /dev/stdin '**/*.js'`
assuming it is run inside /community and /enterprise.

This update improves internal code annotations so developers get more accurate suggestions while working on Odoo's web interface. It helps speed up development and reduce mistakes, with no direct change to end-user features.

This commit adds and fixes type annotations to give more accurate
autocompletion for javascript.

This update refines internal JavaScript configuration so developer tools can catch issues more clearly while working. It helps maintain code quality and productivity without changing how business users interact with Odoo.

This update simplifies and modernizes the JavaScript development tools used by Odoo Enterprise. It prepares automated quality checks to run more easily on changed code, helping teams improve code consistency over time without affecting end users directly.

- Use of jsconfig instead of tsconfig
- jsconfig deployed with tooling, no need for CLI
- ecmascript bumped to version es2022 (static properties)
- prettierrc merged inside the eslintrc
- add a few globals
- cleanup package.json scripts
- add script to lint/format only the diff (opposed to staged files)
- bump up node packages versions
- use eslint as cli instead of prettier-eslint, as eslint does provide parsable output for runbot.
- add the typescrit types of libs as dependencies + main.d.ts to improve autompletion.

This upgrade makes it easier to deploy and use the js tooling, as it is expected more and more people will use it if a lint check is added to the runbot.

About the runbot:
The commit gets the code ready to enable the lint on the runbot. It will lint the code with the same rules and same ignore file. The only difference is the runbot will check only the diff and not the entire commited file.
The goal will be to progressively (and aggressively) whitelist modules to converge to a nice formatted codebase.

This change updates accounting-related filters to work after an underlying account field is removed. It helps keep asset and automatic transfer workflows functioning correctly without changing how business users operate them.

Since `is_off_balance` field is being removed from `account.account`, the domains have to be updated accordingly.

Spreadsheet-related apps were adjusted to work with the latest spreadsheet library update. This helps keep document spreadsheets and spreadsheet editing reliable after the underlying component change, with no major workflow changes expected for users.