This update makes it easier for users to find production stock locations and configure the right interim accounts on them. It also improves the product category accounting form by placing key valuation journal and account fields more prominently.

Description of the issue/feature this PR addresses: Ease encoding of interim accounts on locations

Current behavior before PR:

Desired behavior after PR is merged:


Task : 2161057

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

Record change logs in Mail are now generated later in the save process, so multiple edits can be combined into one clearer update. The improvement also captures changes to stored calculated fields, giving users a more complete and reliable activity history across affected apps.

Improve tracking by generating the tracking message at flush.
Also implement the tracking for stored computed fields.

Odoo now prevents reducing the number of decimal places for a currency once accounting entries already exist, avoiding rounding changes that could affect posted financial data. Users are also warned when increasing decimal places so they understand the accounting impact before proceeding.

If accounting entries have already been generated by this currency, we now forbid setting it a lesser number of decimal places (so, higher rounding factor). We also display a warning when increasing the number of decimal places, to make sure the user is aware of the impact it'll have.

The website form builder now uses the left-side options panel, making form editing more consistent with other website editing tools. This improves the editing experience for teams configuring helpdesk and website forms without changing the end-user form behavior.

* = website_studio

The form builder is now using the left panel option system.

This update improves the reliability of field change tracking across several Odoo Enterprise apps. It fixes edge cases that could affect manufacturing maintenance updates, field service billing settings, and holiday work-entry performance tests, helping ensure data is saved and reported consistently.

Counterpart of odoo/odoo#41554.

Sales orders created from field service tasks now use the warehouse assigned to the responsible user, such as a technician's van or an employee's shop. This helps businesses track stock usage more accurately by employee location while keeping the existing default behavior when no user warehouse is set.

Purpose
======
Our current integration between FSM and Stock works well for basic flows, but quickly shows limitations. We don't handle warehouse by employee. Use-case: each worker has a dedicated van with a dedicated stock. I want to track the material used for each intervention to make sure that nothing is stolen.

+ This is also useful in usecases outside of FSM. Example: I have 3 shops (= 3 warehouses), each employee works in a different shop, the default warehouse set on the Sales Order should be the default warehouse of the salesperson. So this should be done sale_stock (and not in FSM)

Specifications
===========
Add a 'Default Warehouse' field on the user only visible if :

- sale_stock is installed
- the 'multi-warehouses' feature is enabled
- domain should only include warehouses which belong to a company the user has access to
- not required

The field should be editable by a user on his own profile and by the admin on all users.

When creating a FSM task from scratch, adding some products creates a SO, the warehouse on the SO should be the default warehouse of the user set on the FSM task.

On SO creation,  set the 'default warehouse' selected on the user assigned to the SO. If there isn't any 'default warehouse' set on the user, fallback on the current behavior (warehouse with
lowest sequence)

The field on the res.user should be a property field to allow multicompany usage.


Related to : https://github.com/odoo/odoo/pull/44257
Task : 2166382

Accounting-related numbering has been aligned with the latest core system changes after journal-specific sequences were removed. This keeps financial documents and related payroll, subscription, reporting, and follow-up flows consistent with the new five-digit default numbering format.

Task [2146469](https://www.odoo.com/web?debug=1#id=2146469&action=333&active_id=967&model=project.task&view_type=form&menu_id=4720)

The sequences of journals have been removed in community.
* The field sequence_id of account.journal has been removed
* Sequences now have a padding of 5 digits by defa

Portal users can now send messages directly without the page refreshing. This makes conversations smoother and helps users continue their work without losing context or waiting for a full reload.

Description of the issue/feature this PR addresses:
Task-ID: https://www.odoo.com/web?#id=2054662&action=327&model=project.task&view_type=form&menu_id=4720