In this commit, we perform the below changes:
 - add a 'tags' m2m field below the SOL one
 - add a 'tags' configuration menu with an editable, optional, and
   multi-edit list view and  set a random color automatically on
   newly created tags
 - In the list view:
     move the SOL field to the right of the task_id one
     move the company_id field to the left of the 'start date' one
     add the tags field to the right of the SOL one
 - kanban view: display the tags field below the task_id one
 - search view: add a quick search on tags
 - search view > filters: rename the 'unpublished' filter into 'draft'
 - add a 'my department' filter that should return the shifts assigned
   to employees who are in the same department as the current user
 - display the 'i take it' button in secondary if the role set on the shift
   is not one of the roles of the current user
 - search view > filters
    - remove the separator between 'to schedule' and 'employees on time off'
    - move the 'employees on time off' filter below the 'shifts in conflict' one
    - move the shifts in conflict/employees on time off / to schedule filters
      below the 'my team' one (with a separator in between them)

task-2700231

## Purpose

### Customer Rating in Helpdesk

Before this changes, the Helpdesk use the customer satisfaction to show the rating average for a Helpdesk Team. This compute was made only in Helpdesk, since in the related community PR, we also use the rating average this compute is made in the `rating.mixin` to avoid duplicate the field and its compute. As in the tasks in the project app, the last rating value is used to determine the final satisfaction of the customer for a ticket. But the final result could be done the last work doing in this ticket and not the result for the global work done in this ticket.

To do this, the idea of this change is to use the rating average to globally see the customer satisfaction of a ticket or even a Helpdesk Team based on the customer satisfaction of each ticket related.

### Add `group_use_rating` group

A new group is added for helpdesk app, it is called `group_use_rating`. The idea of this group is the same then the one for SLA feature called `group_use_sla`. The idea is to add the group of the helpdesk user when at least a helpdesk team has the 'Customer Ratings' enabled. When no helpdesk team has the feature enabled then we remove the group.
With this group, we are now able to show/hide filter only used for this feature is enabled/disabled.

For planning, when `sale_planning` module is installed, the user can set a SOL to a shift (`planning.slot` model). Moreover, if this user has no access to Sales app, then he can even open the form view of the SOL when he is in the form view of a shift with a SOL. This behavior is not expected and remove this permission to grant it only if the current user has access to the Sales app (at least the `sales_team.group_sale_salesman` group).

task-2671848

Community PR: odoo/odoo#81027