zope5: Since 5.8.1 missing Content-Type HTTP header is interpreted as application/x-www-form-urlencoded.

Zope.git:
  commit 5b324f6c461f5ea1cc069739b6c32a1a5ff59df9
  Date:   Thu Jan 19 07:15:18 2023 +0100
    replace `cgi.FieldStorage` by `multipart` (#1094)
    * interpret a missing `CONTENT_TYPE` as `application/x-www-form-urlencoded`

With cgi.FieldStorage, it was interpretated as text/plain so Content-Type has to
be provided now (even for WebDAV despite RFC 4918 stating that it *SHOULD* be
provided).

Some Unit Tests did not provide such header at all but this was wrong (such as
erp5_stripe:testStripe where the real request has application/json as
Content-Type and not text/plain).

The ssl/x509 were renamed after we decided to change the name of the
holding property sheet during the code review. The code was updated,
but not this form

  Otherwise it gets other unrelated objects from a full text search

This is tested in test_14_multiple_workflow_different_permission_roles

See merge request !1982

Otherwise
  https://example.com/foo
would match
  https://example.com/
but not the language-selector
  https://example.com/en/

and not as manager, as some scripts in the workflow have proxy roles, so
it would be nice to test them too.

The CA certificate can be stored on the connector (it is obtained from
the clammit instance).

To store properties related to x509 certificates, used for exemple in
TLS connections

When commiting from ERP5, they are always alphabetically ordered.
So commit the list of property sheets ordered alphabetically to ease to decrease
the number of diffs when commiting from ERP5.

   Fix inconsistency on guard and permissions

   Fixup the inconsistent restart/restart_action transition, that has
     Assignee/Assignor guard in am inconsistent matter.

   Allow assignor have the same permissions and guard than the assignee

   Fix up permissions on delivered state, where the Assignor had no
   permission to view/access accounting period (so deliver by assignor
   only was impossible).

See nexedi/erp5@bcd82831

See nexedi/erp5@bcd82831 (comment 216152)

The main query to the hateoas web section must be cache by the browser,
to reduce the number of queries by 2.

Caching policy manager conditions are checked before calculating the query result,
and so, it is not possible anymore to wait for the script to explicitely
ask for the result to be cached.