This PR makes the following improvements:
->Remove 'remaining hours percentage' measure from task analysis. -> change 'total hours' into 'total hours spent' and 'working days to assign' into 'Working Days to Assign'.
->In pivot view and graph view of task analysis report, following measure will be appear as hh:mm.
  -overtime, total hours, working hours to close, working hours to assign
->Hide the value if it is equal to 0 for the following measures:
  -hours spent, overtime, progress, total hours, working hours to assign,
working days to assign, working hours to close, working days to close ->When calculating the average the following measures should exclude records with a value of 0
  -progress, working hours to assign, working days to assign,
    working hours to close, working days to close.
->Set the by default grouping for the following task analysis report
   -for pivot view add the group by 'create date>month' and made changes
     following changes in measure :
     -count, working hours to assign, working hours to close, total hours
   -for graph view add the group by 'create date>month>project'.

task-3514437

List of features this PR implements:

- add a 'chatbots' menu under the 'configuration > tags' menu item / add a '-> configure chatbots' link that should redirect users to the configuration > chatbots menu
- /search_tickets command: if there are more than 5 results, display a 'load more' button

### Implementation details

For the search_tickets command:

This command triggers the method _execute_command_helpdesk_search_, it now calls a new method _fetch_ticket_by_keyword_ that return the msg containing links to the tickets corresponding to the query, by default the fetch tickets return only 5 tickets, if there are more than 5 ticket corresponding to the query a link *load more* will be added to the messages. 
When clicked this link will rpc call _fetch_ticket_by_keyword_ to fetch 5 more tickets this time, the steps can be repeated until all the tickets are fetched.

To know if there are more tickets corresponding to the query than returned, we try and fetch one more ticket than the limit (so if we're at 5 we try to fetch 6 tickets), the last ticket will be removed from the list and the load more link will be added to the message

The ticket fetching is ordered by 'id desc', fetching first the *6* tickets with the highest id corresponding to the query. The sixth tickets is ditched but it's ID is saved in the button tags so it can be recovered in the frontend to be given back to the backend in case the user clicks on load more.
Once clicked the backend will only fetch ticket with ID lower or equal to the last ticket ID.

Community PR: https://github.com/odoo/odoo/pull/131702

Task-3186593

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Steps to reproduce: (only in a production environment)
- Install l10n_ar_edi
- Switch to an Argentinian company (e.g. (AR) Responsanble Inscripto)
- Create an invoice in "Electronic Invoice (FE)" journal:
  * Customer: [an Argentinian one] (e.g. Belgrano Cargas Y Logistica S (Mipyme))
  * Journal: Electronic Invoice (FE)
  * Document Type: (201) ELECTRONIC CREDIT INVOICE FOR SMBs (FCE) TO
  * FCE: Is Cancellation? (in "Other Info" tab): [NOT CHECKED]
  * FCE: Transmission Option (in "Other Info" tab): [anything]
  * Invoice Lines: Tax 21% and the total amount must be greater than 1000000
- Confirm the invoice
- The invoice must be rejected by customer (that's why a production environment is required)
- Create a credit note:
  * Document Type: (203) ELECTRONIC CREDIT NOTE SME SMEs (FCE) A
- Click on "Reverse and Create Invoice"
It is not possible to send the credit note because its "FCE: Is Cancellation?" property should be checked as the invoice has been rejected, but there is no way to do it.

Solution:
Add "FCE: Is Cancellation?" option in the reversal wizard.

opw-3379792