Purpose
=======

Introduce a "manual" merge mode.

Indeed, while the current rules introduced some "ongoing hygiene", one may wants
to take manual action to "clean up one's database". For example, because one is
working on a report (pivot table, o-spreadsheet, ...). Or because one is able to
take a more drastic approach (merge records that aren't technically the same to
reduce the amount of noise, ...).

The objective is to allow the user to select multiple records on a model to open
the data_merge deduplicate view with the records them selected to merge them
quickly.

Specification
=============

Add a button on ir.model view that allow the user to enable the Merge contextual
action on the current model.

Once the merge action is enable, the user is able to select multiple records and
open the data_merge deduplicate view targetting only the records them selected.
The selected records are placed in the same merge group.

In Data_merge/configuration, user can find the list of models in which the merge
action has been activated.

By default, display the "Merge" option in the action menu for the following
models:

crm.lost.reason
crm.tag
event.tag.category
product.category
project.tags
project.task
helpdesk.ticket
helpdesk.tag
res.country
res.country.state
res.partner.category
res.partner.industry
res.partner.title
utm.campaign
utm.medium
utm.source

As some models already have custom merge methods, the generic merge action
should not be activated on those models, notably:

crm.lead
res.partner
account.analytic.line

Technical implementation
========================

In order to to know on which model the data merge has been activated, a new
boolean field "merge_enabled" has been added to ir.model. This cannot be a
computed field as we would need to execute a search on the code of server
actions to be sure we look for the correct entries.
This field is set after enabling or disabling the merge action on the model and
is not used as a boolean widget to trigger the enabling or disabling of the
server action. Only action buttons on ir.model form view can be used by the
admin to do so.

As some models have already their own merge methods or wizard, we added a class
attribute that is used to avoid enabling the generic merge action on those
models, as multiple merge action would co-exist and because models with custom
merge methods have too specific merge rules to be used in a generic way.
That class attribute is _disable_data_merge and is not necessarily added in
data_merge bridge modules to avoid multiplicating the modules only to add a
class attribute.

Link
====

Task ID: 2459416
COM PR: odoo/odoo#68960

PURPOSE

Have an overview of the current status of a project and keep track of its progress. Share with other stakeholders where the project stands. Identify risks and opportunities and act on them accordingly.

This PR extends this behaviour for both enterprise-limited views and mobile devices.

SPECIFICATIONS

1) Status in controlpanel + access rights
- Indicate the status of the project next to its name in the controlpanel clicking on the status should open the updates kanban-list
by default, the status should be 'on track'
- users with the project > user access right level can see the status of the project
- users with the project > admin access right level can read, write, create, delete updates

2) Project Updates
- Project updates are defined with a name, Author, date, progress and description.
- The description is build based on project data, timesheet related to project and project profitability.

3) Project Updates Kanban View
- The kanban is a kanban list view with a right side panel.
- The right side panel displays various information about project
- It's possible to create milestone from the project update right side panel.

4) Project form view
- The milestone and update lists are accessible from the project form stat buttons

task-2393768

Community : odoo/odoo#68899