Catalog seems to correctly handle the OR parameters.

Do not lose the possible external `query` parameter.

Test jumping to the same context.

Test also direct form rendering configured as jump action.

This allows getting stable URL which can be used in ERP5JS to highlight the current jump

See merge request nexedi/erp5!1261

See merge request nexedi/erp5!1264

runTestSuite accept a --test_node_title argument, which is used in
createTestResult API call, so that task distributor can keep track of which
node executed which task, but since it was not passed, we did not know which
test node executed which test result line.

See merge request nexedi/erp5!1205

Remove some unused code and enable coding style

See merge request nexedi/erp5!1263

Change the conditions from getAggregate to hasAggregate and add a portal_type filter
of getPortalDocumentTypeList, since in reality these check for Attachments that are Document Types
stored in ERP5, so types like 'Internet Message Post' should not be considered.

Plus, xml changes, since there was no commit in these fields in the last 9 years

ZODB Components: Migration dialog: list_selection_name must be explicitly named for mapply() to pass it from REQUEST.

Payments made on the date of previous bank statement but not at 00:00 were
not taken into account in this constraint, which leaded to false positive preventing
to open the next bank reconciliation when previous one had a payment with an
accounting date on the day of the bank statement but not at 00:00

Instead of only checking that an error is reported, check the expected
error message, so that we are sure that this test really covers what
it's supposed to cover.

Now that testnode client is supposed to pass test node title,
make sure that on the server side we can display this information.

runTestSuite accept a --test_node_title argument, which is used in
createTestResult API call, so that task distributor can keep track of which
node executed which task, but since it was not passed, we did not know which
test node executed which test result line.

This was never finished and would probably not be implemented this way,
so let's remove.

ERP5 functional tests are failing too often, until we improve the tests or the
code so that we don't have these intermitent failures, restart the failed tests
a bit automatically.

This is of course not good, because it's hiding problems, but the current state
of the test suite with many randomly failing test makes that we sometimes miss
when permanent failures are introduced.

See merge request nexedi/erp5!1206