See merge request nexedi/erp5!1889

See merge request nexedi/erp5!1887

 Move Simulation to priority 3 helps to not block/delay immediateReindex
 on a scenario where everything is expanding. We use priority 3 to match
 what is used in SimulableMixin.updateSimulation and Delivery.localBuild

This fixes compatibility for python3, especially with hash randomization
(PYTHONHASHSEED) turned on.

This also enables coding style test that was not running for this bt,
after fixing everything flagged by coding style test.

See merge request nexedi/erp5!1892

Make sure we see *all* warnings, both in the tests and in the logfile in production.

Fix many warnings by updating imports and calls to deprecated APIs

See merge request !1879

for consistency and because it's probably good to let user choose
sending mode.

This matches the form title

When producing DSN report, there was a few places where we depended on
dict iteration order, so the test did not pass when running with
PYTHONHASHSEED (erp5_payroll_l10n_fr:testDSNSocialDeclarationReport
fails with PYTHONHASHSEED 323). In these changes we add sorts to some
places where we were iterating on dicts so that the order of the Lines
is deterministic even with hash randomization enabled.
Co-authored-by: Nicolas Wavrant <nicolas.wavrant@nexedi.com>

test was simplified not to use difflib, unittest does a good job of
explaining the differences when using splitlines on long texts, no need
to compute a diff ourselves.

   Without this the redirection places value unquoted causing parser to fail
   later on when resolve {n.me}.

   came_from cannot be None so we simplify the block a bit.

See merge request nexedi/erp5!1888

This makes it easier to find the problematic listbox and also report
once per listbox.

See merge request nexedi/erp5!1870

Set speed with setTargetCoordinates instead of a separate function because some drones API have an unique call for setting both coordinates and speed and the rate of this call can be curbed.

fix expected timestamp as its value is now floored to milliseconds

See merge request nexedi/erp5!1885

It was using "Reference" instead of the dedicated term "Currency Code".

Attribute Unicity constraint message was not correctly including the
reference, the error message was always "Another currency with reference
None already exists".

See merge request nexedi/erp5!1877

    Use a form, so we do not have to hardcode the resource.

   Also include a minimal message.