This improve the compatibility with ERP5JS

It will reduce the HTML size and prevent any browser parsing incompatibility.

ZODB Components: erp5_banking_core: Fix testERP5Banking{AccountingCancellation,BankAccountInventory,CheckDeposit} failures.

BankingOperation monkey patches several ERP5 basic classes to add getBaobab* methods.
With ERP5Banking Product on FS, BankingOperation was imported at Zope startup when
loading Products and monkey patches were applied.

Moreover, since this was added and because of a bug in bt5 implementation of
provide dependencies, it was not possible to install this bt5 from TemplateTool
on a fresh instance:
  [...]
    File "product/ERP5Type/tests/runUnitTest.py", line 417, in _installBusinessTemplateList
      with_test_dependency_list=True)]
    File "product/ERP5/Tool/TemplateTool.py", line 1200, in resolveBusinessTemplateListDependency
      return self.sortBusinessTemplateList(list(bt5_set))
    File "product/ERP5/Tool/TemplateTool.py", line 947, in sortBusinessTemplateList
      "Circular dependencies on %s" % reverse_dependency_dict.keys()
  NotImplementedError: Circular dependencies on ['erp5_mysql_innodb_catalog', 'erp5_banking_core', 'erp5_property_sheets', 'erp5_core', 'erp5_pdm', 'erp5_trade', 'erp5_accounting', 'erp5_core_proxy_field_legacy', 'erp5_simulation', 'erp5_base']

  -> erp5_banking_core depends on erp5_trade.
  --> erp5_trade depends on erp5_base.
  ---> erp5_base depends on erp5_full_text_catalog meta bt5 resolved to erp5_banking_core (provision_list).

This fixes testBanking* Unit Tests failures since ERP5Banking migration to ZODB
Components (0d2bd4c0) not triggered with FS Unit Tests because it does not try to
resolve dependencies and just install them in getBusinessTemplateList() order.

ZODB Components: Cosmetic: Remove Unit Test FS-only getBusinessTemplateList() now that it has been migrated.

ERP5Site: Do not override newContent() but use FolderMixIn implementation to have a consistent behavior.

ERP5Site was raising error when ID or portal_type was not passed but there is
no reason to do so (as it is done in FolderMixIn.newContent()). This allows
calling ERP5Site.newContent(temp_object=True) without ID, likewise Folder.

Folder: Allow to create temp_objects anywhere, without checking if it's in allowed types for that Portal Type.

Until now, creating a temp_object with newContent() required for the temp_object
to be in allowed types. However, this was inconsistent with (now deprecated)
newTemp*() functions (calling directly constructInstance()) not having such
limitations.

Besides lifting such limitation being needed to properly replace newTemp*() calls,
portal_trash.newContent() pattern is already commonly used used here meaning there
is a real use case.

This also fixes testBanking* failures: newTempCashDeliveryLine() created objects
on 'Cash Inventory' and latter call Delivery.isAccountable() which does not exist on
portal_trash.

See also 04b49859.

/reviewed-on nexedi/erp5!1025

Also hide seconds as it weights down the interface, and to follow the behavior of XML style

This is an empty modules whose names are dynamically inserted by
AccessControl.Implementation.

These constructors are not recognized by pylint and now we have
no-name-in-module errors.

Because since introduction of portal types as classes there was this
idea of deprecating those in favor of using newContent(temp_object=True,
switch to this new syntax.

Since we still have to create documents in portal_trash, only change the
minimal to get coding style tests passing again.

/reviewed-on nexedi/erp5!1024

for Person_viewAssignment form

For example, ExtensionClass (such as ValidationFailed) need to have their AST properly
generated. This fixes 'Use of super on an old style class (super-on-old-class)' error.

Besides of being needed for bootstrap, this also makes more sense than ignoring
completely ERP5Type as some modules should not be in there and should be migrated.

ZODB Components: Preparation of erp5_base migration from FS: LoginAccountProviderMixin implements ILoginAccountProvider (otherwise unused).

this is not passed correctly in submission script anyway, so selection
is not taken into account in this case

Especially important as the deleted document has an hard-coded ID which gets reused - as is the case here.

It may not be a good idea to hardcode such ids in tests too, but I cannot judge at a glance.

/cc @romain

/reviewed-on nexedi/erp5!1020

Assorted fixes for minor issues with ZODB History tab:

1. When viewing history of a website or websection in the "backoffice" interface, clicking on *View ZODB History* does not keep the `ignore_layout:int=1` request parameter that forces displaying the forms in the *View* skin selection.
2. Fix using ZODB history for documents with binary properties, such as `data` property on images and files. Instead of failing with unicode error, just display "(binary)". 
3. Put the link field in center group, forms with only fields in left group and nothing in right group have a border only on the left side. ( this is  https://www.erp5.com/documentation/developer/guideline/module/erp5-Guideline.Module.Creation/#listbox-only-tabs-should-have-a-read-only-title-in-center-group )

see before:
![before__1_](/uploads/eaafe271228e960f58b7b928cb517ac9/before__1_.png)

and after:
![Screenshot_2017-11-28_at_19.32.09](/uploads/bdd0adcc80b138dca7ddcb45b2ff184a/Screenshot_2017-11-28_at_19.32.09.png)



/reviewed-on nexedi/erp5!512

This is enabled for title and description only, because that's usually
what we put on "external" documents such as invoices.

By "resource" here it means products, services, components and their
individual variations

In short, change the translation configuration from 
![Screenshot_2017-12-05_at_10.22.39](/uploads/2c72a0b35dbbde1ec6d7156f2e2f372a/Screenshot_2017-12-05_at_10.22.39.png)

to 

![Screenshot_2017-12-05_at_10.23.31](/uploads/d86c2fce6a9d134e17b5fddc983491a3/Screenshot_2017-12-05_at_10.23.31.png)


/reviewed-on !515

Fix broken tests after !1011 it was merged too fast.

/reviewed-on nexedi/erp5!1018

Some users have been using google chrome builtin translation system with
ERP5 back office (xhtml style), but the way google translation changes
the DOM sometimes break ERP5 interface.
This also have data privacy issue as this translation is done on google
servers.

https://www.w3.org/International/questions/qa-translate-flag recommends
using translate=no but the approach of the meta tag might be preferable
for our case as it prevents sending the page content to translation
service.

/reviewed-on nexedi/erp5!879

The field needs to be in center group to comply with
https://www.erp5.com/documentation/developer/guideline/module/erp5-Guideline.Module.Creation/#listbox-only-tabs-should-have-a-read-only-title-in-center-group

It was failing decoding unicode

Otherwise we cannot use this feature on a website/websection using
a different skin selection.