Original PR description

Before this commit, if a user deletes a message before the recipient sees it, the notification stays in the recipient's discuss and when the recipient tries to click on "1 new message", they get a traceback.

Steps to reproduce:
1. Send message as Mitchell Admin to Marc Demo
2. Delete said message
3. Open the conversation as Marc Demo
4. Click on the new message banner

The traceback happens because the highlighMessage hook tries to access a non-existing message.
This commit fixes the issue by:
- Adding a guard when accessing the message on the highlightMessage hook
- Sending a bus message to notify the front-end of a message deletion
- Changing the compute of the message unread counter as not to count deleted messages

Original PR description

### Steps to reproduce the issue:

1. Create a Purchase Order and add Analytic Distribution to one of the Product Lines
2. Make sure the "Budget" Smart Button is visible
3. Create a User with no Accounting access rights and maximum Purchase access rights
4. With Purchase User, open the Purchase Order
5. Receive following Access Error:

>     You are not allowed to access 'Budget' (budget.analytic) records.
>
>     This operation is allowed for the following groups:
>     	- Accounting/Bookkeeper
>     	- Accounting/Read-only

### Explanation:

When accessing `purchase.order`, a list of computes starting with `purchase.order._compute_above_budget` will cause the user to perform a `search` on `budget.line`, which he does not have access to without `account.group_account_readonly` or higher.

### Fix reasoning:

Since the user will only perform a `search`, `sudo` is all indicated to bypass the Access Rights restriction.

opw-4244187

Original PR description

PoS receipt should show fiskaly information but they are not shown

Steps to reproduce:
-------------------
* Setup you db with fiskaly
* Start a PoS and sell any product
> Observation: The receipt doesn't contain any information

opw-4216415

Original PR description

Currently, a traceback is occurring when the user clicks on the consolidated balance.

To reproduce this issue:

1) Install `account_consolidation`
2) Create a new record in `consolidation` by filling the required fields 
3) Now open the `dashboard` of consolidation
4) Click `consolidated balance`

Error:- 
```
KeyError: 'date'
```

When the user creates a consolidated record, there will be no date in the options.

Which leads to a traceback when the date is accessed from the options.

https://github.com/odoo/enterprise/blob/c42f33ee588d07eb5147a4db6bbf5080155a0b9b/account_reports/models/account_report.py#L4811-L4812

https://github.com/odoo/enterprise/blob/c42f33ee588d07eb5147a4db6bbf5080155a0b9b/account_reports/models/account_report.py#L4765-L4766

After applying this commit, we can resolve this issue by prechecking the date in the options. By doing this we can make the code more robust.

sentry-5731169111