in case the message is defined in the field ('manage_messagesForm' tab)

instead use ValidationError.getMessage API

Depending on how the message is defined.

Before this commit, translation happened typically in higher level,
where the error message was rendered.
but this imposed translation in everything, including mapped messages,
pulluting Localizer with unneeded messages.

This commit introduces getMessage, the logic is:
- If the message is defined in the code that raises, then it should be translated there
- If the message is defined in the field (in 'manage_messagesForm')
then we need to translate in ValidationError class. Caller should
pass translation_service, because we do not want to import it in Formulator

Like xhtml style

renderJS's mutex must be used instead

If enabled, accessing the 'View' skin selection will raise an Error.

2 alarms are provided to automatically enable/disable xhtml style for some period of time.

Some users can be always continue using xhtml style.

And add related field to CredentialUpdate_view

This reverts commit 6430ccc3.

because it's redundant with the fact that we can already distinguish different Trade Model Line within the returned function by using .getAmountGeneratorLine() on the first parameter.

Extend coding style tests to check forms:

* [Method Name Is Prefixed With Portal Or Meta Type, Class Or Interface](https://www.erp5.com/documentation/developer/guideline/programming/erp5-Guideline.Programming.Naming.Conventions/#method-name-is-prefixed-with-portal-or-meta-type,-class-or-interface) / [Set Document Form Ids To PortalType_view](https://www.erp5.com/documentation/developer/guideline/module/erp5-Guideline.Module.Creation/#set-document-form-ids-to-portaltype_view) - this was checked for python scripts, but not yet for dialogs
* [Form Name Uses Lowercase View After Portal Type](https://www.erp5.com/documentation/developer/guideline/programming/erp5-Guideline.Programming.Naming.Conventions/#form-name-uses-lowercase-view-after-portal-type)
* [Dialog Form Name Is Postfixed With Dialog](https://www.erp5.com/documentation/developer/guideline/programming/erp5-Guideline.Programming.Naming.Conventions/#dialog-form-name-is-postfixed-with-dialog)
* [Report Name Uses Portal Type Followed By View Report Name And Report](https://www.erp5.com/documentation/developer/guideline/programming/erp5-Guideline.Programming.Naming.Conventions/#report-name-uses-portal-type-followed-by-view-report-name-and-report)
* [Place Simulation And Validation Fields At Bottom Of Right Group](https://www.erp5.com/documentation/developer/guideline/module/erp5-Guideline.Module.Creation/#place-simulation-and-validation-fields-at-bottom-of-right-group)
* [Use Correct Names For Simulation And Validation Titles](https://www.erp5.com/documentation/developer/guideline/module/erp5-Guideline.Use.Correct.Names.For.Simulation.And.Validation.Titles)

and apply minimal fixes to all business templates already running coding style checks.


See merge request !1021

There are too many forms to rename, it will be done later

Also fix its copy/pasted description

Since jquery_sheet_editor adds actions to Web Table (which are in dms) it
needs to depend on dms for the tests.

This dialog does not seem to be referenced, the action is probably missing

these forms are not dialogs, they are included in reports. Because dialog
forms need to follow the X_viewXDialog naming, scheme, make these forms
use form_list instead, the result is same.

not referenced and breaking several guidelines rules

not used

The portal type name is ERP5 Scalability Distribut*or*

this was changed in 6560ac6d (erp5_code_mirror: Update to 3.22., 2014-07-23)
probably by accident