The project customer preview now hides non-validated timesheets when the invoicing policy only allows validated timesheets. This prevents internal preview users from seeing a different task view than customers see in the portal, improving billing transparency and consistency.

### Issue:

Due to this issue, in the project sharing, the customer preview doesn't reflect the actual behaviour of the portal view. It shows non-validated timesheets even if invoicing policy is validated timesheets only.

#### To reproduce:
1- Create a db with sale_project and sale_timesheet_enterprise
2- Configure invoicing policy to validated timesheets only
3- Create a service product:
- Create on Order: Project & Task
- Invoicing policy: Based on Timesheets

4- Create a Quotation for the product and confirm it
5- Open project from smart button
6- Share project with a portal user with Edit access
7- Open tasks, and add two timesheets to the task
8- Open timesheet app, and validate one of the timesheets
9- From project page, click on Customer preview
10- In preview, open the task. You can see both timesheets which is a different behaviour if you view the project using portal user. Using portal user, only validated timesheets are shown.

### Cause:

The timesheets are filtered here to only show validated timesheets:

https://github.com/odoo/enterprise/blob/8223ed0765c6064b88280656a5ab6b13ca9a431f/sale_timesheet_enterprise/models/project_task.py#L73-L91

However, it is filtered only if user is portal. In customer preview the user is still the internal user, as a result the timesheets will not be filtered.

To fix that we can check if project_sharing_id exist in context to filter timesheets.

opw-5093339

Forward-Port-Of: odoo/enterprise#97470

This update adjusts many enterprise module tests so legacy installation behavior is set automatically. It helps keep post-install checks consistent by default, reducing maintenance work and avoiding mismatches in automated validation.

Reference and selection field values are now sorted in test simulations the same way they are defined, rather than alphabetically by the stored value. This makes automated Gantt-related tests more reliable and better aligned with real expected behavior.

selection and reference fields are not sorted according to the selection value index, but using the value itself.

Note: this could be fixed in earlier version, but since it's an API change (of the mock server, but still...), it could break tests of existing custom modules built by the community.

Task: 5102923

Fixed an issue where opening a tax report from a Luxembourg return for a previous month incorrectly reset the date filter to the current month. This helps users review and file past-period returns with the correct reporting dates.

This commit solve an issue when being on the Luxembourg and doing a return on a previous month like may and clicking on the link to the tax report on the return, the date filter was wrongly set to this month.

no task id

Asset names can now be shown and imported in the user's selected language. This improves usability for companies operating in multilingual environments and helps keep asset records understandable across teams.

To support multilingual environments, this commit refactors the 'name' field on the asset model with `translate=True`, converting it to a standard, translatable text field.

This allows asset names to be imported and displayed in the user's selected language.

task-5122900

The asset list was changed back so users can open the full creation form when they click New. This restores the expected workflow and avoids confusion when creating new assets.

The previous change to make the asset list view editable caused a problem where the "New" button no longer opens the form view.

This commit reverts that change to restore the intended functionality.

Forward-Port-Of: odoo/enterprise#97483

Error messages in US payroll and NACHA payment flows now use the same bank field label that users see on the form. This makes it easier for users to identify which bank detail needs to be completed or corrected.

The label shown in the res.partner.bank form view depends on the show_aba_routing field. If we don't show the correct label in these error messages it's not clear to the user what field they have to fill.

task-5052996

Forward-Port-Of: odoo/enterprise#97510
Forward-Port-Of: odoo/enterprise#97318

This update makes IoT payment terminal logs more complete and consistent. Each transaction step now includes identifying details, making it easier for support teams to trace issues and resolve payment problems faster.

This PR improves the logging of terminals used with iot box. We will now get a log for every step of a transaction along with some information identifying the transaction

Forward-Port-Of: odoo/enterprise#97216