This reverts commit 527d688e.

Do not access form submission REQUEST from the listbox list method,
as it is rendered asynchronously in ERP5JS

This reverts commit 35b2c024.

Allow edition in the new UI

This make everything slow as hell and prevent to quickly save.

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

Updater was using this command to find the latest revision modifying a
path:

  git log -1 -- $PATH

but because of git log's history simplificiation [1] when the head of
the branch is a merge commit, the considered revision was not the merge
commit but its parent.

Use --full-history so that git does not simplify history and return the
merge commit if the latest commit is a merge.

[1]: https://git-scm.com/docs/git-log#_history_simplification

See also https://stackoverflow.com/a/50724301/7607763

instead of randomly truncating the existing file, which sometimes does
not cause an invalid index, create an invalid index from scratch.

I used this blog post
https://mincong.io/2018/04/28/git-index/#2-inside-gitindex for a
description of the index format.