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 )

See merge request nexedi/erp5!1875

See merge request nexedi/erp5!1873

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.

See merge request nexedi/erp5!1871

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.

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

erp5_officejs_appstore_base: do not use deprecated script ERP5Site_getAuthenticatedMemberPersonValue

Parameter `partial_text_match` added

Fixup 84281a2a

Correct the naming because this takes a zip file content as argument, so
it expects bytes not string

This improves readability when activity_kw, args or kw are big.

Having a form which allows sending emails with arbitrary senders,
recipients, and content, sent using the site's mail setup, is a recipe for
sending spam and destroying one's mail system's reputation.

See merge request !1872