When new password does not match policy, in reset password and change
password dialogs, we used u' '.join([str(message) ...]) to join all
translated messages in a string, but this construct will decode the
str(message) to unicode using ascii, so it will fail when these messages
contain some multi bytes characters.

Extend test coverage to check that these dialogs uses translations and use
non ascii messages in the tests, to make sure we don't have regressions
with this issue.

See merge request nexedi/erp5!1001

ERP5 does not handle user "account" anymore, it handles "login".
Please use "Add ERP5 Login" or any other login you need instead.

See discussions on nexedi/erp5!547

Enable coding style on erp5_run_my_doc since it now gets installed with erp5_officejs

See merge request nexedi/erp5!1325

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.

remove useless language="javascript"
remove useless <col>

This fixes these errors:

    Using nu validator to parse the view "TestPage_viewEditTest" (from erp5_run_my_doc bt) with warnings displayed :
    Error: line 623 column 33 : Table column 1 established by element “col” has no cells beginning in it.: st_table">
        <col class="action_column" />
        <
    Error: line 624 column 33 : Table column 2 established by element “col” has no cells beginning in it.: n" />
        <col class="action_column" />
        <
    Error: line 625 column 11 : Table column 3 established by element “col” has no cells beginning in it.: n" />
        <col />
        <
    Error: line 626 column 11 : Table column 4 established by element “col” has no cells beginning in it.: ol />
        <col />
        <
    Error: line 627 column 11 : Table column 5 established by element “col” has no cells beginning in it.: ol />
        <col />
        <
    Warning: line 619 column 85 : The “language” attribute on the “script” element is obsolete. You can safely omit it.: r.css">
      <script language="javascript"
              src="http://erp5-catalog-0:2201/portal_3010166623124138150/test_editor.js"></scri
    Warning: line 621 column 90 : The “language” attribute on the “script” element is obsolete. You can safely omit it.: script>
      <script language="javascript"
              src="http://erp5-catalog-0:2201/portal_3010166623124138150/erp5_run_my_docs.js"></scri

Don't use inline <style> in a <div>, but in an external <link>.

This fixes:

    Using nu validator to parse the view "TestPage_viewTestReport" (from erp5_run_my_doc bt) with warnings displayed :
    Error: line 581 column 23 : Element “style” not allowed as child of element “div” in this context. (Suppressing further errors from this subtree.): "><div  >
    <style type="text/css">
    body,

These translations where creating too many messages

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