Invoicing contain views for Invoice Line and Invoice Cell portal types,
but does not contain portal types to contain Invoice Lines. Add
erp5_advanced_invoicing as a test dependency so that during HTML tests
we can create invoice lines in Sale Invoice Transaction (or maybe
Purchase or Internal, only one path will be tested)

Accounting Rule Cell only exist in erp5_accounting_simulation_legacy

The dependency is that erp5_ingestion_test depends on erp5_ingestion,
erp5_ingestion has no reason to depend on erp5_ingestion_test.

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.