Purpose
=======

The goal of this task is to address the use-case of law firms, architect's offices, design offices, insurance brokers, etc. that deal with a lot of documents for their projects.
Typically, they handle multiple documents and work on different versions of them.
Once those are validated, they are sent to the customer, who can then download, review, and sign the documents, as well as upload new ones.

Previous behavior
=================

Before this PR, when the feature was enabled, a workspace and default tags could be defined in the settings.
Then, when an attachment was added to a task/project, or contained in a message in the chatter, it would be automatically added to the workspace as a document with the given default tags and linked to the respective project/task.

Changes introduced
==================

- Added a "Use Documents" setting on projects to enable the feature per project.
	- When enabling the feature globally, it will be enabled automatically on new and existing non-fsm projects.
- Moved the "Documents Workspace" and "Default Tags" settings to the projects.
	- Only a workspace with the same company of no company can be selected.
	- Attachments are added as documents in the specified folder with the default tags set on the project and linked to their respective project/task.
	- If no workspace is selected when creating a project, a new one will be created automatically with the same name as the project.
	- When the feature is enabled globally, workspaces are also automatically created for all the projects without one.
	- Only tags from the project workspace or its parents can be selected.
- Introduced a new company setting: "Parent Workspace".
	- If it is set, automatically created document workspaces for projects in this company will be children of this workspace.
	- All existing and new companies will have a default "Projects" parent workspace, which contains some tags, workflow rules and actions.
- Introduced a new company setting: "Workspace Template".
	- If it is set, automatically created document workspaces for projects in this company will be a copy of this workspace.
	- Copies of the workspace include copies of its facets, tags, rules, actions, and child workspaces (recursively).
	- The copy will still have the same name as the project.
	- The workspace template cannot be a parent of the workspace set as parent workspace in the settings
- Added a new link in the portal on tasks: "Documents".
	- This link is ony available if there are documents linked to the task that are also shared through a share link, whether by ids or by domain.
	- This page is pretty much the same as the one you get when opening a share link with multiple documents.
	- You can also upload documents if the folder of the project of the task is shared through a share link by domain (meaning it's either shared directly or by one of its ancestors with the "Include sub-folders" option enabled)
- When viewing the documents linked to a project/task, only the relevant workspaces will be available in the search panel.
	- This includes the workspace of the project, and other workspaces containing documents linked to the task/project
- Added a "Documents" button in the project kanban view, between the "Timesheets" and "Sales Order" ones.

Technical details
=================

documents
---------

Most of the changes here are on `documents.folder`:
- Added a `parent_path`, to make computations involving ancestors/descendants more efficient.
- Added field `is_shared`, which computes if a folder is shared.
	- A folder is shared if there exists a `documents.share` link sharing the folder by domain, or sharing one its ancestor by domain with the `include_sub_folders` set to True.
	- Added a test to check that this field works as intended.
- Added an override to the `copy` method, to allow duplicating folders for the "Workspace Template" setting.
	- The facets and tags are copied automatically
	- This method manually copies the workflow rules/actions linked to a folder to correctly set the tags/facets ids on the copies.
	- It also manually copies the workpace children recursively, because by default, only `copy_data` would be called on the children.
	- Added a test to check that this method works as intended.

documents_project
-----------------

- Added a new "Documents" link on tasks with shared documents in the portal
	- The shared documents page is an override of the page used for `documents.share` links, with most routes changed and share link/tokens dependencies removed
- Added controllers for the new portal routes.
	- Access to most of those routes depends on having access to the corresponding task.
- Added a `is_shared` field on `documents.document`, to compute if a document is shared.
	- A document is shared if its folder is shared (see above) or if there exists a `documents.share` link sharing the document by id.
	- This field is computationally expensive, which is why we decided to put it in `documents_project` and not `documents`.
	- However, it is not stored, as keeping it up to date would be expensive too, and it's only used in two places.
	- Added a test to check that this field works as intended
- Added an override to `search_panel_select_range`in `documents.document` to only include folders relevant to a task/project.
- Changed the search domain for the `_compute_attachment_ids` method in `project.task` to exclude attachments linked to a document.
	- Added the One2many `document_ids` in ` ir.attachments` to make this easier.
	- The field `attachment_ids` is only used in the portal to show attachments, the idea here is to reduce redundancy with the new shared documents page.
- Added a method on `res.company` to automatically create default data.
	- It creates a default "Projects" workspace for the "Parent Workspace" setting, as well as defaults facets, tags, workflow rules and actions for that workspace.
- Added constraints to ensure that the workspace of the "Parent Workspace" setting cannot be a child of the workspace of the "Workspace Template" setting.
- Added constraints to ensure that a workspace is not linked to a project in a different company.
- Added constraints to ensure that the default tags on a project cannot be linked to a folder different than that of the project.
- Added tests to check that the "Parent Workspace" and "Workspace Template" settings work as intended

documents_fsm
-------------

New module, its sole purpose is to not automatically enable the documents feature on fsm project, and automatically enable/disable it when toggling the fsm status of a project.

documents_project_sign
----------------------

New module, its sole purpose is to add a "Sign" workflow action on the parent workspace of all new and existing companies.

-----
Related: https://github.com/odoo/odoo/pull/92044
Related: https://github.com/odoo/upgrade/pull/3557

Task-2802803

Steps to reproduce:
(on a new database without demp)
- create an invoice of 1000$ for every month from November 2021 to April 2022
- In reporting > Balance Sheet
- Select "End Of Last Month"

Issue:
The "Previous Year Unallocated Earnings" will be incorrect != 2000 (1000 December + 1000 November)

Cause:
The issue is not from "Previous Year Unallocated Earnings" per se but from from one of its subcomponent: the "Current Year Earnings"
```
PREV_YEAR_EARNINGS =
    -sum                          : from_beginning
    + ALLOCATED_EARNINGS          : from_beginning
    - CURR_YEAR_EARNINGS_ALLOC    : from_fiscalyear
    - CURR_YEAR_EARNINGS_PNL      : normal            -> Problematic one
        [OPINC + OIN - COS - EXP - DEP]
```
The CURR_YEAR_EARNINGS_PNL or NEP (Net Profit) is computed for the month of April 2022 (04/01/22 - 04/30/222) instead of from the beginning of the fiscal year (01/01/22-30/04/22).
This happens only when you select a "Last of [month quarter]" option (quarter if in the third or fourth one). If you select "Today" or a "Custom End Date", it won't cause the issue.

Solution:
Force a "custom" option value to compute it correctly

opw-2821529

Forward-Port-Of: odoo/enterprise#28022
Forward-Port-Of: odoo/enterprise#27910