Administrators can now configure whether custom fields are copied when records are duplicated and define fields that reflect values from related records. This makes custom data setup more flexible and helps keep information consistent across linked records.

Add fields `copy` and `related` on `ir.model.fields`, with the same meaning as the corresponding attributes on fields.

This update standardizes modal pop-up windows across many Odoo screens so they follow the same Bootstrap-based layout and behavior. Users should see a more consistent experience when completing accounting, budgeting, analytics, and related wizard workflows, with a related web tour test fix to keep automated checks stable.

Task: https://www.odoo.com/web#id=19645&view_type=form&model=project.task&menu_id=3942&action=327
Pad: https://pad.odoo.com/p/r.Y1fLImzP4ay8emS2

As @aab-odoo commented here https://github.com/odoo-dev/odoo/commit/3cbe1b2404847933d013e213139f5c6952092c4f#commitcomment-12708717, which almost changes whole spec so I have created this new PR after review.

Partner and customer records are easier to manage, with clearer choices between companies and individuals and simplified address handling for contacts. The update also streamlines related account, VAT, payment, CRM, delivery, event, HR, repair, and point-of-sale views so users can access key information through cleaner forms and counters.

Add a new selection field company_type, replacing is_company. To keep
backward compatibility, the old field is still stored and considered
as an interface field for the new company_type field. The deprecated
tag is added to ensure people will udpate their module.

The customer form has been redesigned to make it clearer whether a record is a company, individual, contact, or address. Contact lists, kanban cards, customer menus, and related accounting and CRM views were adjusted so users can manage customer information with less confusion.

Task : https://www.odoo.com/web#id=13765&view_type=form&model=project.task&action=327
Pad : https://pad.odoo.com/p/r.rwwROfDJuoEdD3by

This fix prevents deleted records from interfering with automatic updates to related data. It helps ensure business information stays accurate after records are removed, reducing the risk of inconsistent or stale values.

This fixes a nasty bug: after deleting some records, recomputation is skipped on some records.

Here is the explanation of the bug:
- deleting record marks them as "missing" in cache;
- computing fields assigns them in cache, and triggers some invalidation (in cache only);
- the cache invalidation follows the trigger paths in cache, and raises an exception found in cache;
- the raised exception is stored in cache as the value of the record to compute.

The fix is simple: when following trigger paths in cache, skip special values.

This fixes an issue where items created quickly in a Kanban column could lose the column information and not be linked to the correct stage. Users can now rely on quick creation to place new records in the intended workflow column.

… , so it will not get 'id' and object not linked to correct stage.

Issue : https://www.odoo.com/web#id=644638&view_type=form&model=project.issue&menu_id=4120&action=609

The Google account module has been updated to align with Odoo's newer internal API standards. This helps keep the integration maintainable and compatible with current platform practices without introducing major user-facing changes.

Task: https://www.odoo.com/web?#id=12033&view_type=form&model=project.task&action=327
Pad: https://pad.odoo.com/p/r.xjHOIOhlay4JLKQ3