Description of the issue/feature this PR addresses:

The previous implementation of the Bolivian localization was based on Peruvian accounting standards, making it incompatible with local regulations. This PR refactors the module to align with Bolivian accounting and tax requirements.

Current behavior before PR:

The module is currently developed by a Peruvian company and it does not meet Bolivian legal and fiscal requirements.
The chart of accounts lacked key accounts needed for local compliance.
Tax configurations and reports were not aligned with Bolivian tax regulations.
Accounts, taxes, banks, states, and language formats were not properly adapted for Bolivia.

Desired behavior after PR is merged:

The Chart of Accounts now includes 661 accounts, ensuring compliance with Bolivian standards.
67 tax configurations have been added to support local tax regulations.
9 current tax reports are included for accurate fiscal reporting.
Bolivian banks information has been integrated.
The Bolivian states have been added.
Language formatting has been improved for better localization.
This update ensures the module is fully adapted to Bolivian requirements, improving accuracy and usability for businesses operating in Bolivia.
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

This PR aims to remove some global settings to only keep them in the project form view:

1. More specifically, it removes the global settings "Recurring Tasks", "Task Dependencies" and "Milestones" from the global settings.
And moves "Recurring Tasks" and "Task Dependencies" in the project form view directly. It keeps the "Milestones" settings in the project form view as it was.

- The way groups `project.group_project_milestone`, `project.group_project_recurring_tasks` and `project.group_project_recurring_tasks` are given to the user is now different, as the global settings are removed.
It now works like this:
=> When the user enables one of the settings we mentioned (e.g. "Milestones") in any project and the related group (e.g. `project.group_project_milestone`) is not already added to the base user group, it is added.
=> If the user disables the setting from a project/remove a project which had the setting enabled, if after that disabling there is no project (even archived ones) having the setting enabled, then the related group is removed from the base user group.

- The default value given to the setting of a new project is always False.

- We remove the behaviour introduced by this commit: https://github.com/odoo/odoo/commit/50ffc339991b136b48525b2d60aa34a3039bb8da

2. The "Customer Ratings" setting was removed from the global settings and the project form view. It is moved to the task stage form view.

- If the rating status of a stage is set to "stage": when a task reaches that stage, an email will be automatically sent to get the customer rating.
  If the rating status of a stage is set to "periodic": an email will be sent periodically at the given interval as long as the task remains in the stage.
- If sale_project is installed, we only show the setting if at least one of the project of the stage is billable
- The "Rating Email Template" is now required if the setting is enabled.
- Some renaming was made in the setting description to make it clearer.
- The group `project.group_project_rating` is removed so we always make visible the customer rating in all views and in the reporting.

3. When the user enables the top bar a project which only has one visible action (e.g. "Tasks"), it now directly opens the dropdown so that the user will gain time to select the actions to show.


task-4700865

*: mrp, mrp_subcontracting, mrp_subcontracting_dropshipping, purchase_stock

With this commit
=======================

- The operations section is hidden if no routes on the product.
- The 'Manufacture' route now has a higher sequence than the 'Buy' route.
- The 'Buy' route is no longer selected by default for products.
- If a product has no BOM, no MO will be created from Reordering Rules. It will
  give error for create a bom.
- In the Replenishment Dashboard, users can now select the 'Warehouse Selectable' route.
- The 'Buy' route cannot be selected if the product is
  not purchasable (i.e., 'Can be Purchased' must be enabled).
- No need to select routes in the following cases:

     - If purchase_ok is enabled and the product has a vendor,
       the 'Buy' route is automatically selected.
     - If the product has a BOM, the 'mrp' route is automatically selected.
     - If a product is a component of a subcontracting BOM and has sufficient
       available quantity, the 'Resupply Subcontractor on Order'
       route is automatically selected.

- Now, the 'Dropship' route can also work for 'subcontracting BOMs',
  similar to the 'Dropship Subcontractor on Order' route.

Task - [4385221](https://www.odoo.com/odoo/my-tasks/4385221)

*= l10n_be_fiscal_categories, l10n_be_account_disallowed_expenses_fleet

The Fiscal Category system was previously limited to handling Disallowed Expenses in the Belgian fiscal return, where certain expense types had to be declared separately despite being accounted for normally. This limitation, especially in cases like taxis (25% disallowed rate) or specific vehicle-related deductions, led users to create artificial account categories (e.g., "1205.1 Taxi"), reducing the clarity and maintainability of the fiscal report.

This **PR** generalizes Fiscal Categories to support broader fiscal use cases, allowing deduction rates or rules to be defined directly on accounts. It also enhances the Fiscal Report to aggregate and compute all necessary fiscal values more flexibly.

In addition, the **PR** renames modules, models, fields, and XML identifiers from the legacy disallowed_expenses structure to fiscal_categories, improving consistency and clarity. Key changes include:

Modules:
1. account_disallowed_expenses → account_fiscal_categories
2. account_disallowed_expenses_fleet → account_fiscal_categories_fleet
3. l10n_be_disallowed_expenses → l10n_be_fiscal_categories
4. l10n_be_account_disallowed_expenses → l10n_be_fiscal_categories_fleet

Models & Fields:
1. disallowed.expenses.category → account.fiscal.category
2. disallowed.expenses.rate → removed
3. disallowed_expenses_category_id → fiscal_category_id

**task**-4848770

Upgrade PR - https://github.com/odoo/upgrade/pull/7825