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

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.

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

The XML had incorrect categories to non existent paths, fixing the XML
to remove these paths made the warning disappear.

nested warns where it is used and the modern approach for this is
contextlib.nullcontext

EntireQuery pass a PlaceHolderTableDefinition for almost all catalog
searches, so "from_expression" itself can not be deprecated at this
point

We were importing from an old alias in App.class_init, but this module
has been removed from Zope5

This was too late to enable all warnings, many modules were already
imported and already triggered lots of deprecation warnings that were
ignored.

Also, we no longer need to patch warnings.showwarning because we use
logging.captureWarnings(True) in runwsgi. As a result, the log events
will be slightly different, because logging's way of logging warnings
is a bit different.

test_warnings_redirected_to_event_log no longer make sense because we
only use logging.captureWarnings() in runwsgi, while running tests we
want warnings to be displayed on the console so that developer see them.

In runUnitTest environment this is not set up.

By default, DeprecationWarning and PendingDeprecationWarning, and
ImportWarning are ignored, we want to see those while running tests, so
we reset the warnings module to use "default" behavior for all warnings.

https://docs.python.org/3/library/warnings.html#default-warning-filter
https://docs.python.org/2.7/library/warnings.html#updating-code-for-new-versions-of-python

This also implements the recommendation from
https://docs.python.org/3/library/warnings.html#overriding-the-default-filter

> Developers of test runners for Python code are advised to instead
> ensure that all warnings are displayed by default for the code under
> test, using code like:

    import sys

    if not sys.warnoptions:
        import os, warnings
        warnings.simplefilter("default") # Change the filter in this process
        os.environ["PYTHONWARNINGS"] = "default" # Also affect subprocesses

This also extend the "Run Live Test" action to allow controlling the
warnings filter, but on python2 this does not work so well, once a
warning was ignored, later switching to "always" or "error" does not
process the warning again ( it might be because of
 https://bugs.python.org/issue4180 )

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