* "Create Skin Folder" action had a typo, so it was not setting the `business_template_skin_layer_priorty` property that business template is using when installing.
* "Create Report" was not updated for the new "action title" feature of forms.

This time, add the missing tests that should have prevented these problems.

See merge request nexedi/erp5!1133

Enable coding style on erp5_forge, after removing several problematic scripts that did not seem used.

See merge request nexedi/erp5!1134

erp5_corporate_identity: only images with alt attribute specified will be added to the table with images

it was skipped in testXHTML, to enable coding style test for forge we
also need to skip it here.

this is a 10 lines "maybe useful one day" script, we don't need this

I don't think anybody still uses this.

this code is invalid and does not seem used

this code is full of errors and does not seem referenced

the property name had a typo, so it was not correctly used for
priorities

BusinessTemplate_createReport was broken since this argument was
introduced.

Since commit d2b20acd004441d1cb8d36f33ed7ca112dff0d17 on slapos.git we
are using gcc 8.2 which seem to generate slightly faster code, so we
adjust the min time because tests were failing because we are now too
fast.

erp5_corporate_identity: improve slideshow rendering including displaying legacy presentation as slideshow

ERP5: Remove *Capacity and ImmobilisationMovement Documents never used since their introduction many years ago.

Receiving name & password parameters does not prevent us from also
receiving the authentication cookie. It must not be kept in the request.
And likewise for requests also containing an HTTP authentication header.
And likewise for requests for which CookieCrumbler disables itself on.

The reason why root document is being used as serialization_tag is to cover
document which get recursively reindexed: such indexation activity would
not be able to be validated against all the the serializatio_tag of
documents it will process. But here, fulltext indexations are all spawned
per-document anyway, so we can use such per-document values.

Spawn fulltext indexation activity with the same priority as the
top-priority activity part of current activity group.
And expose the priority of current activity (top-priority for grouped
activities).
Ideally, the priority of each spawned activity should be the top-priority
of all activities member of this activity group for corresponding document.
But there is no obvious way to achieve that through indexation API without
increasing complexity significantly.

plus a few python3 fixes for problem that appeared now that we have more test coverage

See merge request !1128

and a few cleanups in test suite

See merge request !1126

This removes some logs happening a lot during tests, when installing business templates or indexing documents.

See merge request !1105