This allow edit scripts or interactions to change the status message or
the status level using the same way as workflow scripts: script can set
the status text in request['portal_status_message'] and the status level
in request['portal_status_level'].

Note that part of this was already checked in accidentally in 97c40dcb

/reviewed-on !1052

When running test.erp5.testHalJsonStyle live tests, the same transaction
seems to be seeing two different users. This cause an incorrect cache hit
with the second user, which then retrieves values computed by & for the
first user.
Fix this by scoping the cache by user id, causing different cache entries
to be used.

testBusinessTemplate: When one Unit Test failed, subsequent tests were failing too as objects remained.

ZODB Components: BusinessTemplate: Products.ERP5Type.Base will never be migrated (InitGhostBase) so ignore it when migrating source files from FS.

All other Component modules must be kept alive during the REQUEST life (f523edc4).
However, Unit Tests modules should be kept alive until it finished executing and
this may span accross multiple REQUESTS.

Issue found out when migrating testBusinessTemplate to erp5_core_test which was
failing as the module was GC'ed and its top-level variables were reset to None by
the interpreter.

Not migrated:
  + testERP5Site: Checks Site creation and overrides setUp().
  + testERP5TypeInterfaces: Verifies that classes implements the Interfaces they claim to implement.
    => Should probably be integrated into coding style Unit Tests and done
       dynamically (MRO). Also, testERP5Interfaces imports code from that
       Unit Test and requires non-core bt5 to be installed.
  + testInvalidationBug: To-do (failing).
  + testPredicate: testDomainTool, inheriting from TestPredicateMixin, should be rewritten to not
    depend on erp5_apparel so that it can be moved to erp5_core_test.

Also, move manuallyInstallBusinessTemplate() and uninstallBusinessTemplate() from
ERP5TypeCommandLineTestCase to ERP5TypeTestCaseMixin as they are also used by
Live Unit Tests.

ERP5Type: {CSS,JS}Packer have never been used so delete them rather than migrating them to portal_components.

This reverts commit 1862fdf5.
Because of current ERP5Type.Core.Folder inheritance order, this commit
is not ready for inclusion in master just yet.

All ERP5UI-visible (hence needing to call allowedContentTypes) BTReeFolder2
instances should already inherit ERP5Type.Core.Folder, removing the need
for this monkey-patch.

In preparation of reordering Folder inheritance order.

An insolvency proceeding represent a justice decision about the insolvency of a person or an organization.

An insolvency proceeding is defined by: an Insolvency Proceeding Type, a Creditor, a Debtor, Judicial Administrator, Judicial Representative.
The insolvency proceeding follow the ticket workflow

Also fix a few copy/pasted test titles.

This test should catch when business templates metadata in `bt/` is different from the actual content in `*TemplateItem/` . It should not happen, but sometimes we can forgot to include one or the other in commit.

This also fixes problems in the currently tested business templates, there was three kind of problems:
 * binary files are now exported with `bin` extension, it use to be `obj`.
 * In several business templates, we export categories as `portal_categories/category/*`, while this looks convenient, it's problematic when categories are added by other business templates, every time developer export the business template they have to consider whether the new paths should be exported or not. This changed to list explicitly all the paths to include in business template.
 * some business templates were partially commited ( "erp5_dms_ui_test:  Add selenium tests" )

/reviewed-on nexedi/erp5!1049

Make it pass coding style

"Hide" an action that is not really useful and problematic when used by mistake

/reviewed-on nexedi/erp5!1051

This way, the substitution mapping method can return a dynamic mapping,
the only requirement is to implement __getitem__

ne use case is to be able to use the same substitution script for
different CRM notification messages and only compute the "heavy"
substitution variables when they are actually needed.

See !1047

This allow edit scripts or interactions to change the status message or
the status level using the same way as workflow scripts: script can set
the status text in request['portal_status_message'] and the status level
in request['portal_status_level'].

Note that part of this was already checked in accidentally in 97c40dcb

We run them in coding style test suite already.

Also these test now need business template repository properly
configured in template tool, which is not set in default setup, so
keeping them working would require extra work.