Form.__call__ replaces page template call, so it is also responsible
to set the content type in response.

With Page Templates, ZopePageTemplate._exec (called by
Shared.DC.Scripts.Bindings.__call__ and _bindAndExec) sets the
response content type and calls pt_render. Form.__call__ also calls
pt_render, so to behave like page template, it should also sets the
response content type.

In erp5_xhtml_style, we don't notice this, because global_definitions
contains a setHeader call to set content type to html.

Check that it correctly includes the web page and sets the content
type header.

it would be good to rewrite this in a page template

This method converts the HTML, so it should escape nasty HTML tags.

Also add missing escaping when inserting the base

and move it to erp5_administration, this is not a "core" feature but
just a developer tool.

It was used in a few tests, move all the tests in testERP5Administration

See merge request !1706

See also slapos.libnetworkcache@319b8b18

See merge request nexedi/erp5!1705

Make sure we don't set grouping reference on lines that have a valid
group only for source (or destination) but not for the other side.

gadget_html_viewer had styles to add a border for tables, so that they
look similar to tables added in CKEditor. One problem is that all tables
had borders, because HTML emails are often using tables to position the
content, when viewing an Mail Message from ERP5 back office interface
we could see all the borders, which looked a bit ugly.

These changes bring back a behavior closer to default style sheet of
browsers: tables have no border by default, but a rule is added to
emulate the rendering of border="1" attributes, so that tables edited
with CKEditor have borders and look the same in the editor or in the
html viewer.

See merge request !1704

Instead of add-hoc ", ".join

This reorganises a bit the tests to include the proxify feature of
ERP5 Form in ERP5 Form test

helpful to get an overview

Remove title, we don't need title and reference, because title is
acquired from reference, so they have the same value.

Add Causality, it can be useful for example to search in the module.

Add "more columns" for all properties from the view of a stripe session

This is now detected by coding style test

```py
kw = {...}
kw['metadata[key]'] = 'value'
connector.createSession(**kw)
```

but it would be more beautiful to be able to write it like this:

```py
kw = {...}
kw['metadata] = {'key': 'value'}
connector.createSession(**kw)
```

This would need change in the way the request data is serialised in
createSession.

This fixes things like:
  portal_catalog(source_reference={'query':'foo OR bar', 'key':'KeywordKey'})
or:
  portal_catalog(query=AutoQuery(source_reference='foo OR bar', key='KeywordKey'))

So we get:
  (`...`.`reference` LIKE '%foo%' OR `...`.`reference` LIKE '%bar%')

instead of:
  `...`.`reference` IN ('{\'query\': \'foo\', \'key\': \'KeywordKey\'}',
                        '{\'query\': \'bar\', \'key\': \'KeywordKey\'}')

Also, remove default values as it makes it easy for caller to leave arguments
out by mistake.
Also, use positional arguments as they are faster than named arguments.

See merge request !1698

this makes it easier to select the value by copy and paste.
Without the space, when double clicking on "value" in "key:value",
all "key:value" gets selected, with the space, only "value" gets
selected.

Invoking Zuite_waitForActivities when portal_activities is already
subscribed and while another thread from this process is already
executing activities causes infinite "Got a lock error, retrying...".

This situation happens when developer makes a mistake (runs the
tests without unsubscribing activities), so be nice to the developer
so that they don't have to restart Zope.

It's enough to set on the class and if we don't have it on instances, it
saves a few bytes in pickles

There have been a regression recently

Depends on nexedi/slapos!1290

See merge request nexedi/erp5!1695

When installing scripts or components from a business template, set
the _erp5_coverage_filename property so that the plugin is able to find
the corresponding code from the business template filesystem
representation.

coverage might use these to compute the upload URL for coverage data