Test error tracebacks are now logged as a single grouped entry instead of many separate lines. This makes runbot logs easier to read, search, and copy when diagnosing failed tests, while removing less useful test docstring text from short descriptions.

Traceback coming from tests are currently logged
line by line. This will implies that runbot will have one
ir_logging entry per line which is not practical. More than
that, the log prefix can make the traceback less readable
because of line returns and difficult to copy paste.

This commit simply remove this feature. After discussion with odo
and chs, we will also remove the docstring from test shortDescription
since most of the time this information is not clear and can be accessed
in source code if needed.

Website and web controller pages now ignore unexpected extra URL parameters instead of failing. This makes public pages more resilient when visitors arrive through marketing links, debug links, or other URLs that add extra tracking details.

Before this commit, call a controller defined as: 

```python
@http.route('/route', type='http', auth='public')
def controller_func(self, foo):
    do_it()
```

and called with url like /route?foo=1&bar=2

will crash with an exception:
`TypeError: controller_func() got an unexpected keyword argument 'bar'`

Now, we remove the extra parameters if the controller doesn't support it.
This case is not uncommon, you can easily arrive in this case with utm or
debug as extra parameter.



--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

The documentation was updated to match the current structure for test assets and JavaScript test files. This helps development teams follow the latest project organization and reduces confusion when maintaining or adding tests.

Adapt doc to d7cd97a9b

This update prevents crashes when a user works in a different company than their employee record. Leave management now checks accessible employee information first, improving reliability in multi-company setups.

--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

This change updates an internal translation test so it no longer conflicts with similar sample selection values from another test module. It helps prevent intermittent test failures, improving confidence in translation-related development without affecting end users.

export.selection.withdefault and export.selection both have a selection field
with Foo and Bar as possible selections.
When doing
`self.env["base.update.translations"].create({'lang': 'fr_FR'}).act_update()`
the base.update.translations wizard exports the translations of ALL modules,
including the ones of the test_impex module.

The generate po entry is something like:
```
  #. modules: test_impex, test_translation_import
  #: selection:export.selection,value:0
  #: selection:export.selection.withdefault,value:0
  #: selection:test.translation.import,import_type:0
  msgid "Bar"
  msgstr "Bar in french"
```
but may also be
```
  #. modules: test_translation_import, test_impex
  #: selection:export.selection,value:0
  #: selection:export.selection.withdefault,value:0
  #: selection:test.translation.import,import_type:0
  msgid "Bar"
  msgstr "Bar in french"
```
(not sure where the indeterminism comes from)

which creates 3 translation entries that are sometimes linked to the module
test_impex (ignored when exporting the translations of test_translation_import)
but are sometimes linked to the module test_translation_import instead

In the second case, this makes 3 more translations that is was supposed to
exist.

This commit hides the symptom by making sure there is no longer a clash
when exporting the translations of the module test_translation_import.
A real fix to avoid creating unnecessary translations during an execution of
the base.update.translations wizard must also be made in the future.

It is assumed the unnecessary translations problem was already present before
a7621137cb0d75ec545152d5e1d413c9d3548e45 but polib introduced the indeterminism
making the test fails from time to time.

JavaScript test runs will no longer mark slow startup checks as warnings that can fail automated status checks. This helps teams avoid blocked merges when there is no actual product issue to resolve.

In JS tests, when the ready code takes too much time, a warning is
logged. As a consequence, the runbot updates the github status as a
failure, causing real pain to people who simply wants to merge their
features.

With this commit the warning is changed into an info and the runbot will
be happy.

This fixes a timing issue where simultaneous cart and product information updates could interfere with each other during checkout. Customers should see more consistent cart behavior, reducing the chance of errors when adding products or loading product details.

Payroll leave calculations now use the work schedule set on the employee's contract rather than the employee record. This helps ensure reported leave days and hours match the actual contractual schedule used for payroll.

In order to have the real number_of_days/number_of_hours we need to use
the calendar defined on the contract of the employee instead of using
directly the employee's calendar