This fix prevents an error from appearing when users open the Timesheet list view in developer mode. It aligns the Timesheet list view configuration with the expected format, improving reliability for teams reviewing timesheet entries.

- 1  Issue
        ListRenderer pros type is array/list and timesheet_grid inside pros type
    is object, both mismatch so i think this issue is raised.
- 2 Fix:
  We have replaced object with list type in list renderer pros.

Step to reproduce:
 - Install Timesheet
 - Turn on developer mode
 - Go to timesheet
 - Click on listview

task- 3507986

This update corrects syntax mistakes in Web Studio page templates that could cause errors in certain screens. It also supports better automated checks so similar template issues are caught earlier, improving reliability for users.

New test from community catches syntax mistakes of qweb files.
This PR fixes those issues.
 https://github.com/odoo/odoo/pull/128445

Performance test benchmarks were adjusted to match recent underlying platform changes. This keeps internal test checks accurate and helps avoid false failures in development workflows, with no expected impact on end users.

This commit modifies the query count of some performance tests to cope with changes made in https://github.com/odoo/odoo/pull/131355

task-3442819

The event barcode setup now updates registration barcodes in one batch instead of many separate database calls. This reduces installation time and database overhead, especially when the database is hosted separately, while focusing barcode generation on current and future events.

## Description
During the installation of the module `event_barcode`, we have an override of `_init_column` for the `barcode`. We were using the psycopg's `executemany` which is just a syntactical sugar for a loop over an `execute`. So we trigger 1 query (which incurs a network cost when deployed and the database is not on the same machine) per row, currently we have 27 queries (for demo data).

## Solution
We can use SQL syntax:
```sql
UPDATE ... SET ... FROM (VALUES ...) WHERE ...
```
which does 1 update for all rows in one go.

## Implementation details
We could implement this query directly with a simple execute, but it requires a lot of manual construction with the help of `sql. Composed`, because of necessity to insert manually `sql.Literal` used for the tuples of the `VALUES`.
Psycopg2 exposes a function called `execute_values` which is just for this case and makes to code way more legible.
We also generate barcodes only for registrations linked to event that are ongoing or in the future, to improve the speed of the UPDATE itself (we update less rows).

## Reference
task-3430406

The Belgian fleet expense calculation now shows rates as percentages instead of decimals. This prevents misleading values such as 0.5 appearing where 50 should be shown, helping users apply the correct disallowed expense rate.

Currently the rate is incorrectly computed (0.5 instead of 50)