erp5_web_renderjs_ui: keep previous focus color

* add color in the commit tree
* send one json only
* display the list of removed files in the gadget diff
* translate gadget
* desactivated changelog

See nexedi/erp5@ea219b74

erp5_force: break by dropping the custom page template

erp5_forge: drop vcs_dialog

erp5_forge: use Base_redirect

erp5_forge: use formulator to propagate the values

erp5_forge drop some fields from changelog form

erp5_forge:

erp5_forge: stop accessing the request to pass arguments

erp5_forge: commit from xhtml_style and from erp5js

erp5_forge: remove comment

erp5_forge: drop useless comment

erp5_forge: useless import

erp5_forge: revert & update action

erp5_forge: handle SVN exception

erp5_forge: drop log

RSVP.Promise cancel callback do not expect a Promise as result.
In order to handle potential errors triggered by setButtonTitle, run it in an renderjs's job.

See merge request nexedi/erp5!1285

We no longer run tests with `python setup.py`, but simply with `python -m unittest`

With nexedi/slapos!862 we no longer need this

See merge request nexedi/erp5!1316

See also https://github.com/zopefoundation/ZEO/pull/63
     and nexedi/erp5!1095

No error in testCMFActivity and testConflictResolution.
For the only error in testInvalidationBug, see comment.

But this commit is not enough for ZODB5. The only known issue so far
is the use of newer pickle protocol, which breaks export of ZODB data
and requires non-trivial changes in our XMLExportImport/ppml code.
So for the moment, many failures in testBusinessTempate.

erp5_web_renderjs_ui_test: reproduce validation error issue and add asserts to make sure field has expected class

* Trigger focus and blur to test renderjs functions properly
* Add asserts to make sure we don't lose value after raise Invalid Date
* Cover issue that invalid class does not disappear after click to create new object Foo in relation input
* Make sure fifth_failure input has invalid class
* Cover validation error to multicheckbox, checkbox and radio fields

* change the label field to not display the error text by default
* change all html5 fields (input, select, textarea) to add a custom *invalid* class when the field is invalid
* change all html5 fields to listen to the `focus` and `blur` event (with the renderjs onEvent method)
  Then, acquire (with `declareAcquiredMethod`) and call `notifyFocus` / `notifyBlur` methods respectively.
* change the label field to handle `notifyFocus` / `notifyBlur` (with `allowPublicAcquisition`).
  Change the validation error text display state depending on the field status
* Trigger onStateChange to set invalid class. If error comes from input field, we need to change state locally to set invalid class
* Regenerate gadget_erp5_nojqm.css from  erp5less.css using http://lesscss.org/less-preview/
* Textarea gadget should not prevent default when invalid event is triggered
* Support notifyFocus and notifyBlur in panel

Users with only view permissions in accounting should not be offered to use
the grouping reference fast inputs, because grouping transactions is a kind
of modification.

Listbox title is automatically translated, calling translation explicitly
is wrong here.

erp5_officejs_support_request_ui does not yet supports translation fully,
but we start testing translation.

For now only home page and panel are covered.

For the need of this test:
 - depend on erp5_l10n_fr because we'll test in french
 - modify test service so that its title is translated to french (and depend
   on erp5_content_translation for easier management of these translations)

Resource reference can be useful for example with cases where resource
titles are not uniques, or when some classifications are codified in
resources references.

crm/officejs_support_request_ui: use "resource__translated__title" as Support Request Type in listboxs

In other places, we always show the translated service titles.

By using resource__translated__title, this enable the new syntax for
translated related keys from aee8bcac (ERP5Catalog/content_translation:
support translated related keys, 2020-10-07), so that column can be searched
or sorted.

Let the catalog decide what can be searched and sorted, instead of
duplicating the list of column. It has same effect and is easier to maintain.

Term is "Support Request Type".