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

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".

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

   Also include a minimal message.

expand always reindex the full simulation tree, even if there is nothing to do.
This is cpu costly.

No need to generate simulation expand error

* copy all aggregate values
* expand source/destination project defined on the open order
* expand source/destination payment
* support Open Order Cell
* if there is no stop_date, block the generation to today

If 2 lines have the same effective date (catalog has a 1 second precision),
always return the validate and open first.

Commit: 02d06501ce38bc24d5d045968a53017d9b96b312

Changes applied from history:

http://git.erp5.org/gitweb/erp5.git/history/refs/heads/interaction-drop:/product/ERP5/Document/SubscriptionItem.py?js=1

   Include some symbols to allow this script to be more complaint with erp5_authentication_policy, and more common practices of password settings.

   I explicity didnt include string.ponctuation because it introduces some unusual charts that are not commonly found on passwords like brackets, braces, angle brackets...

This makes ERP5JS's datetime field behave same as python when using
TALES expression for "date_only" and other less used field values.

Co-authored-by: Romain Courteaud <romain@nexedi.com>

 - no more "false" string false
 - empty arrays are false

"false" string evaluating as false allowed to use ?editable=false
in the URL to force a page to render as non editable. This was probably
used only in the tests. The support of this was moved to the form page
gadget.

This script has no reason to be an exception to user's title retrieval
permissions.
Non-ERP5 users do not have applicable access control, so handle those
cases specifically. Such users may be:
- since-deleted ERP5 users
- coming from acl_users/zodb_users
Use a generic placeholder when the user is not allowed to see a
transition's actor.

This allows configuring what URLs can be ingested, by default, no URL
can be ingested.