In case of erp5_core business template update this code is called (with update=True argument)
and thus it will effectively override previous portal_alarms' state which
is wrong as no "general purpose" code should overwrite potential
developer configuration.
Tests passing at https://nexedi.erp5.net/test_result_module/20200324-3BC4D696 thus merging right away.

See merge request !1086

See merge request !1050

business template update this code is called (with update=True argument)
and thus it will effectivly override previous portal_alarms' state which
is wrong as no "general purpose" code should ovewrite potential
developer configuration.

Also extend coding style test to cover this kind of issues with business templates.

See merge request !1083

This caused upgrader errors such as:

    Error: Web Site web_site_module/ooffice_spreadsheet references a non existant appcache gadget_officejs_spreadsheet.appcache

This caused upgrader errors such as:

    Error: Web Site web_site_module/officejs_smart_assistant references a non existant appcache gadget_officejs_spreadsheet.appcache

We want to detect business templates with problems that would prevent to
run upgrader.

Mimic xhtml style.

Deleted Device Document as it is not used anywhere and not really useful:
Item can be used instead.

Migrated SubscriptionItem from FS to erp5_open_trade: this is the contract as
in https://www.erp5.com/erp5-TechnicalNote.Open.Order#contract and make
erp5_payroll depends on erp5_open_trade as Employment Contract is a
SubscriptionItem and, per design, Payroll is kind of an Open Order.

ERP5TypeInformation are used for Portal Types of Portal Types and needed to generate at
least Workflow Methods early at Zope startup (initializePortalTypeDynamicWorkflowMethods()
and portal_type_group_filter in the problem reported on MR 1032) for very basic Portal
Type classes (such as Category Tool). So, Leave these on the filesystem for now, we can
eventually deal with them later if necessary.

There is no need to crash the renderjs interface for an error not related to the interface itself.

contentValues() nowadays return also non ERP5-ish objects such as python
scripts , OFS.File etc. Because of that, if an ERP5 Folder contained a
non ERP5 object, which does not have fixConsistency or checkConsistency
methods, Folder.checkConsistency was causing an infinite loop because it
was acquiring checkConsistency method from self.

See merge request !1076

base, trade, pdm, mrp and dms

See merge request !1073

previous version would keep only one file ending in 'translation_data.js'
which was buggy. The scope here is to return all files,
but put those ending with 'translation_data.js' first,
so that it is more user friendly for user following the convention.

Again for user friendliness, we sort the lists alphabetically also

See merge request !1075

so that several activities can happen for the same Person.

Sometimes these API fail, but that's not so important, what matters is marking commits as success or failure at the end of test.

erp5_accounting is installed before auto-configurtion and is unreliable thus use erp5_trade which certainly is installed by configurator.

This MR continues !1074  (Ivan's mistake)

See merge request !1077

Add a business template that can configure a default ERP5's installation. This bt5 is to be used in Scalability and Deployment tests ONLY.

contentValues() nowadays return also non ERP5-ish objects such as python
scripts , OFS.File etc. Because of that, if an ERP5 Folder contained a
non ERP5 object, which does not have fixConsistency or checkConsistency
methods, Folder.checkConsistency was causing an infinite loop because it
was acquiring checkConsistency method from self.