This fix resolves a visual problem where the MRP work order display showed a black box in dark mode instead of properly adapting to the theme. The update ensures the display looks correct and consistent whether users are working in light or dark mode by using Odoo's color scheme instead of Bootstrap's default styling.

Instead of using the `bg-white` class from boostrap, which is translated to black in dark-mode, make use of the color-scheme from odoo. This avoids having a mismatch between light and dark mode.

Before (Dark / Light):
![image](https://github.com/user-attachments/assets/566b0897-2120-4c4d-a68e-78dd62dbc5b0)

After (Dark / Light):
![image](https://github.com/user-attachments/assets/55d4dde1-b2fe-4eaa-b215-e01b05cddee0)

This update fixes a missing required field in the Swiss payroll sickness insurance form view. The field was not properly configured in the system interface, which could have caused issues when users tried to enter sickness insurance information. This fix ensures the form displays and functions correctly for HR teams managing Swiss payroll.

Fixed an issue where appointment booking buttons with custom formatting would incorrectly route users to all appointments instead of the specific appointment type they selected. The fix ensures that styled buttons properly direct customers to their intended appointment type by accounting for nested HTML elements within the button.

Issue
-----
When adding formating to an appointment button linked to a specific type of appointment, the button will lead to all appointments instead of just the specific type.

Change
-----
Since buttons can have custom formatting, this will add HTML elements inside the button element. Therefore, we need to take into account that the target of the event may not be the button itself.

opw-4080512

This fix ensures that branch companies can properly access and report on unaffected earnings accounts from their parent company in general ledger and trial balance reports. When both a company and its branch are selected, the system now correctly sums the financial movements on the unaffected earnings account, providing accurate financial reporting across the organization.

On the general ledger and trial balance, the branch company needs to get access to the parent unaffected earning account.

Also if a company and a branch is selected, we need to sum the moves on the unaffected earnings account.

opw-3937063

Users with proper timesheet access permissions can now create invoices for sales orders with validated timesheets without encountering access errors. The fix adjusts permission checks to properly recognize authorized users, enabling the invoicing workflow to function correctly when timesheets are locked and validated.

## Issue:
- A user with sufficient access rights to timesheet, ('User: all timesheets' or 'User: own timesheets only') cannot create an invoice for a sales order within a specific timesheet period, receiving the error: 'Timesheets before [PERIOD] are validated and cannot be modified.'

## Steps To Reproduce:
- Edit `Create on Order` of the `Service on Timesheets` product to be `Project & Task`.
- in settings:
        - enable the `Lock Timesheets` option.
        - set the invoicing policy for Timesheets to `validated timesheets only` .
        - set the invoicing policy for Sales to 'invoice what is delivered'.
- ​Update the timesheet access for `Marc Demo` and set it as 'User: all timesheets'.
- Create a SO with `Service on Timesheets` as a product.
- On the related Task create a timesheet for period 01 May to 31 May and validate it.
- With Marc Demo click on Create an Invoice on the SO, for the same period notice The Access Error.

## Solution:
- in `check_if_allowed` I modified the condition to check if the current user is not a superuser.

opw-3965532

Forward-Port-Of: odoo/enterprise#65435

This fix resolves issues with scanning GS1 barcodes that contain packaging information for tracked products. Previously, when scanning such barcodes, the system failed to retrieve packaging data and lot/serial numbers correctly. Now users can successfully scan and process tracked products with packaging using GS1 barcodes, improving warehouse operations efficiency.

Before this commit, when scaning a GS1 barcode containing a packaging for a tracked product and a lot, it doesn't work.

This commit fixes two issues:
1. Get back packaging data (product and quantity) when a GS1 barcode is scanned;
2. Be able to find the lot/serial number when a GS1 barcode with no product but a packaging is scanned.

Forward-Port-Of: odoo/enterprise#67947
Forward-Port-Of: odoo/enterprise#67727