To reproduce the issue:
1. Switch to the `Activity` view for the Documents module.
2. Click `+ Schedule Activity`.
3. The dialog box opens up with the list of documents.
4. Try to DRAG & DROP any document list item.
5. We get a TRACEBACK.

Issue:
- The `onRecordClick` and the `onDragStart` events bound on the record rows are
  executed when we DRAG & DROP or click the records from the list of documents.
- When the method(`onDragStart`) is called from inside the `Dialog` scope, the
  `foldersById` in the line of code below returns a singleton object(`{false: {…}}`)
  with `false` being the folder_id of the `All` workspace.
- However, when the same method is called from the list/kanban view
  (i.e. outside of the `Dialog` scope) then the `foldersById` would return an
  object with all of the folderIds present as keys.

- In our case `foldersById[record.data.folder_id[0]].has_write_access` throws a
  traceback because the value of every `record.data.folder_id[0]` is a `Number`
  (as no document can be present inside the `All` workspace), but the
  `foldersById` object only contains the `false` key.

Fix:
- The schedule activity dialog box renders the JS of the list view of the related module. In our case, it renders the base list view from the documents and renders the JS of it.
- We cannot change this in stable so we fix the issue in JS.

After this commit:
- The records are no longer selected.
- We no longer get the traceback.

Task-3727009

Forward-Port-Of: odoo/enterprise#56356

Contains four improvements for HMRC flow:
1- Successfully connecting to HMRC now shows a notification to let the user know they can send their reports.
2-  The "send" button in the send HMRC wizard triggers the sending but nothing happens UI wise. Now, the wizard is closed and a confirmation notification is shown.
3- For a user wanting to submit the VAT report for two companies, after switching clicking on the "send to HMRC" button raises an error as the token does not correspond to the correct company. Before, the user had to manually remove their authentication credentials to allow for a new connection to get a new token. Now, if we get an error from HMRC that the agent isn't authorised to submit the report, we clear the credentials ourselves and redirect the user to the login page, so they could get the correct token.
4- Trying to send the report without selecting an obligation returns a traceback error. Now, the send button will not appear unless an obligation is selected.

task-3696341

Forward-Port-Of: odoo/enterprise#55988

Before this commit the Whatsapp Sent Count (located in the Communication tab of the event view) wasn't including messages sent to the attendees who weren't confirmed.

### [This commit changes]
Event mail scheduler will include seats_uncofirmed into calculation of the mail_count_done which is the count of emails sent. This is reflecting the actual number of messages sent.

### [Reproduce]
- Install whatsapp_event
- Create event E starting in time T (Events/Events)
- Add an "Unconfirmed" attendee
- Add an E-Mail in the Communication tab of the event E
	- Set Interval time > T,
	- Template: "Email Reminder"
	- Trigger "Before the event"
- Run scheduled Action sending whatsapp (Scheduled Actions / Event: Mail Scheduler)
- BUG: message sent, but not included in the sent count in the communication tab of the event E

Related to the commit in the odoo community called: [FIX] event: Include unregistered attendee emails in total sent count

# Related PRs in odoo Community
This Pr is a part of fix/test bundle. For more details check out the here Community PR: https://github.com/odoo/odoo/pull/153795

opw-3693626

Forward-Port-Of: odoo/enterprise#60065
Forward-Port-Of: odoo/enterprise#58428

Some of the non canononical timezones are not present in Ubuntu Noble, it would be a better practice to only use canonical timezones in data and tests.

Note that this is not a real fix for all cases since the database that ran on Ubuntu Jammy and are moved to an ubuntu Noble server will have the issue with timezones already in database.

One of the possible fix would be to manage that during upgrades, but this isn't a verry flexible solution since upgrade are meant to manage chyange of version, not change of server. If an old 17.0 versions needs to be moved to a Noble server, this won't work.

Another solution would be to install package like tzdata-legacy that may keep the old timezones but it is not the only think since TAI-10 are also in this package. This solution is not ideal because non canonical timezone will still be shown in the dropdown. We would need to filter them.

A last solution would be to add the support for those old timezones by monkeypatching the lib. This way, only new timezones would be shown but non canonical one won't crash when used. This is not ideal either because we may need to keep this for a while. But in combination with the upgrade solution, it may work proprely.

Forward-Port-Of: odoo/enterprise#60219
Forward-Port-Of: odoo/enterprise#59440