Do not access form submission REQUEST from the listbox list method,
as it is rendered asynchronously in ERP5JS

This reverts commit 35b2c024.

Allow edition in the new UI

This make everything slow as hell and prevent to quickly save.

Example: <h2 class="foo">bar</h2> => <h3 class="foo">bar</h3>

Changing the language and browsing to another web section require to fully refresh the page.

This breaks the previous gadget API.

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

This test uses pinDateTime to create an history of test results where tests
have been executed in order test suite 1, 2, 3.
This is done using this pattern:

      now = DateTime()
      ... # do several things that may actually take more than one second
      self.processTest("test suite 1", "r0=a", node_title="COMP0-Node1")
      self.pinDateTime(now + 1.0/86400)
      self.processTest("test suite 2", "r0=a", node_title="COMP1-Node1")
      self.pinDateTime(now + 2.0/86400)
      self.processTest("test suite 3", "r0=a", node_title="COMP1-Node1")

My guess is that we take "now" too early, and when we add 1 second to this
now variable, this may actually be going back in time sometimes, effectively
creating test suite 2 before test suite 1.

Assign now to current date after doing all the affectTestSuite calls should
solve this.

Portal Type as Classes: Interaction Workflows methods could be improperly generated because of 58d4ab8e.

1. Add Interaction on _setSourceReference() to `Document Component`.
2. generatePortalTypeClass() is called recursively and an inner `Document
   Component` Portal Type class is created without any accessor holder.
=> As __bases__ is (klass, GetAcquireLocalRolesMixIn) since 58d4ab8e but loadClass()
   was not updated to reflect this, Portal Type Workflow Methods were generated on
   the inner Portal Type Class where _setSourceReference() is not available and
   registerWorkflowMethod() creates a WorkflowMethod calling Base._doNothing.

The performance of a module is much less impacted by the number
of objects than before, at least for kind of total we have in
tests (about 1000 objects)

Round the amounts line by line when validating transactions balances and
showing the totals on an accounting transaction.

Even though float field configurations do not allow users to input transactions
where amounts uses more digits that what makes sense for the selected currency,
we had cases where some transactions generated by custom scripts were "too
precise" and passed the validation because unlike in all reports where we
display sum of rounded values, the check was only rounding the sum, which cause
some transactions with 1.00 on one side and 0.333333 0.333333 and 0.333333 on
the other side to be valid.

The scripts used to display sums on an accounting transaction had the same
problem, they were also showing the rounded sum and not the sum of rounded
values.