The event website tour could fail to start because of an internal compatibility issue after a recent framework change. This fix restores the tour flow so users can complete event-related guided steps as expected.

Before this commit, the user got a traceback saying:
```txt
TypeError: Cannot read properties of undefined (reading 'apply')
    at EventAdditionalTourSteps._get_website_event_steps
```
the reason of that issue is because a [recent generic change reviews](https://github.com/odoo/odoo/pull/125716)
`patch` function and so `this._super` no longer exists and has to be
replace by `super` as we extend a method of a class extended.

This commit adapts the additional steps adding via `patch` function
to be able to add those steps and start the tour as expected.

Corrects a settings filter so it compares matching value types, avoiding unexpected results. This helps ensure the relevant configuration options are shown or hidden reliably for users.

Comparing integer and string does not have the expected result

This fix corrects the alignment of the confirmation message that appears when users validate their timesheets. The notification now displays in the proper centered position, improving the visual presentation and user experience when submitting timesheet entries.

Before this PR when we validate timesheet toast notification was not correctly centered.
After this PR when we validate timesheet toast notification is correctly centered.

task-3433667

This update removes an outdated field called "show_operations" from the manufacturing work order form view. The field was already removed from the core system, and this change ensures the enterprise version stays synchronized with that update, preventing display errors and maintaining consistency across the application.

In COM PR linked, `show_operations` field is removed from the form view inherited here.

COM PR: odoo/odoo#140898

This update prevents users from editing the follow-up report directly in Studio, since it's composed only of an email template. Users who need to customize follow-up communications can now edit the underlying email template instead, which is the proper way to modify this report's content.

opw-3551400

Forward-Port-Of: odoo/enterprise#50833

This update completes the cleanup process for the AvaTax accounting module to ensure it's properly neutralized in non-production environments. The fix removes residual production settings that could confuse users even when the module is disabled, bringing the system in line with how it's handled in earlier versions.

This commit adds a missing part of the neutralisation of the
account_avatax app. This brings it back in line with the complete
neutralisation script that is used on the PaaS and SaaS in versions < 16.0

Forward-Port-Of: odoo/enterprise#50889

This update restores a scroll test in the mail messaging system that was previously removed. The fix ensures that the automatic scrolling behavior in the message chatter works correctly and is properly validated through testing.

Fixes in community PR.

https://github.com/odoo/odoo/pull/142308

The aged payable audit helper text was displaying as plain text instead of formatted markup. This fix applies proper formatting to the helper content, improving readability and presentation of the audit information in the aged payable report.

This commit makes the helper of the auditing action of the aged payable report markup as it is currently not the case and its content is in plain text.

This update adds a verification check to ensure that helpdesk teams are properly found during testing. Previously, the system would attempt to update a helpdesk team without confirming it existed, which could lead to silent failures. This fix adds a safety check to catch and report any issues when helpdesk teams cannot be located.

Before this commit, the test does a search to fetch a helpdesk team to do a write but we don't check if the helpdesk is found

This commit adds an assert to be sure a helpdesk team is found with the search called.

runbot-21676

Forward-Port-Of: odoo/enterprise#50997

This update corrects how column labels appear in accounting reports. Previously, column labels were displayed in lowercase, making them harder to read. The fix now displays labels in proper formatting, improving the visual presentation and readability of financial reports for users.

Before this commit we use `column.name` as label of our columns for report lines in the report form view.
It caused that the label was in lower case.
The aim of this commit is using the `label` instead of the `name` to have the column `label` well formatted.

Before:
![image](https://github.com/odoo/enterprise/assets/6582885/8dfa8ccf-3faf-4f19-89a3-1f7bf0b15985)

After:
![image](https://github.com/odoo/enterprise/assets/6582885/a79d0046-0223-44a0-8a19-306a2aefbda7)


no task id

A recent update removed the "plan" button from the sales planning calendar view to reduce clutter. This fix updates the automated test to work with the new interface by clicking directly on the calendar cell instead of looking for the removed button. This ensures the test continues to work properly with the updated user interface.

Before this commit, a recent generic change removes the "add" and "plan" buttons in each gantt cell to avoid having too many elements available in the gantt view. That changes has not been adapted for the sale_planning tour and so the step failed because it no longer found plan button.

This commit removes the step failed and adapt the previous step to just click on the grid cell to display the plan dialog.

runbot-25881

Two automated tests in the Planning and Project Forecast modules were failing when run on weekends because the system's working schedule doesn't include weekends. This fix ensures these tests always run during weekdays by freezing the test execution time, making the tests reliable and consistent regardless of when they're run.

## [FIX] project_forecast: freeze time for test_shift_creation_from_project

Before this commit, the `test_shift_creation_from_project` test failed
during the weekend because the working schedule of the current company
considers the weekend is not a working day and so instead of creating a
planning template during 2 days, it will create a planning template during
one day.

This commit freezes the time to be sure, the test is executed during a
working day to stay valid and keep the same behavior to test.

runobt-41215

## [FIX] planning: freeze time for test_shift_creation_from_role

Before this commit, the `test_shift_creation_from_role` test failed
during the weekend because the working schedule of the current company
considers the weekend is not a working day and so instead of creating a
planning template during 2 days, it will create a planning template during
one day.

This commit freezes the time to be sure, the test is executed during a
working day to stay valid and keep the same behavior to test.

runobt-41977

Forward-Port-Of: odoo/enterprise#50999