This reverts commit e50d05af.

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.

Example: <h2 class="foo">bar</h2> => <h3 class="foo">bar</h3>

erp5_web_renderjs_ui: keep previous focus color

This reverts commit a87db49b.

This front page gadget allows user to:
* create any kind of document
* launch any kind of report
* contribute a new documents

This gadget can be used to replicate the xhtml access page.

fixup! ERP5Workflow: testPerformance: Object creation is slower so increase maximum acceptable value.

0.0062 was still too much, we had test run taking 0.0064, set the threshold
to 0.0066 to be safe.

Sequence produce lots of useless output, which makes it slow to display test
result pages for tests using sequences, like testBusinesTemplate.
It must also be taking a lot of disk space on the server and is generally
not useful, when a test fail we have the log of the failing test.

Let's be consistent and use "Permissions" everywhere.

See merge request nexedi/erp5!1405

In English, "Open" means both the action of openning and the state when something
is open. Several workflows have the problem that the "Open" transition is
translated to something that does not describe the action, but the state.

We have a mechanism to override the translation for a state, by translating
`Word [{state_title} state in {workflow_id}]`, but we don't have such mechanism
for transitions, so when "Word" exist both as a transition and a state, "Word"
should be the translation of the transition and we should have translations in
context for all the workflow states.

Starting from PAS 1.10.0, assignRoleToPrincipal is private, only
manage_assignRoleToPrincipals can be used from restricted python.

We do nothing on these methods, but we comply to the interface.

When there is a invalid field, we trigger a notification if the user tries to save the form. But, if this notification is triggered, we don't trigger an alert when the user clicks in another page to leave.

But, if the field is invalid, the user does not click in "Save" and try to leave, the alarm is triggered.

Workflows are ERP5 Document now, we stay inside ERP5JS intead of go to ZMI