* Use single API
   * Unify usage of _simulateScript with the mixin

  This script is a copy the one on product/ERP5/bin/bigfile_client_example.py

   By respecting the dependencies, it is possible to use it on development
   environments to speed up a bit the setup.

  This code was unused since 7 years ago when it was written.

    If the user has just archived OSO, it means he destroyed everything (also).
    Update Tests, Open sale order with no Lines are automatically archived
    Update Test, Email isn't send if there isn't any invoice to cancel for the user.

   It allow us to use renderjs_runner UI for develop and run tests.

   You can create a Contract-Like Invitation, which a preset configuration to be applied into a cloud contract whenever the user input the Token or access it via a specific URL.

   WIP: Squash futher implemenations into this one

    Maximum Invoice Delay defines the delay after due date
    Maximum Invoice Credit defines the max amount after the due date before stop the instances.

  Upgrade dump configuration to help to detected long ago local changes that
  can eventually can exist on production sites.

   * Add tests for SubscriptionRequest_processStarted
   * Add tests for SubscriptionRequest_verifyInstanceIsAllocated
   * Added test for SubscriptionRequest_processConfirmed

    It was rewritten to use a simplified shared API from the Test Mixin

    makeTree requests a simple deployed Hosting Subscription with all elementes, this only replaces the template used when generate the objects.

See merge request nexedi/slapos.core!244

See merge request nexedi/slapos.core!243

The main part is to address the supervisor path too long we sometimes have with theia or slaprunner tests.

Some minor fixes are also included

See merge request nexedi/slapos.core!242

This also makes development easier, because we can make a temporary
change to skip setupModule not to reinstall software when we are working
only on the test and we don't need to recompile the software.

This should make investigation of errors on testnode easiers, any logged
messages by test framework goes to testcase.log

Setup logging at the very beginning, to also have messages logged during
initialization

Also adjust a bit the logged messages, we don't need to log everytime we
snapshot a file or folder, this cause the log to be very big, but it can
be interesting to log when we start and stop checking software, so that
we see how long this took.

See merge request !230

On test nodes, these socket path sometimes exceed the linux limit.