It isn't required to run it that often since everything else will take long, and it perform a too expensive query for run
    it every minute.

   Just save some minor processing time.

  Those are mostly sample files updated for this revision, each project should keep a
  separated dumped files on their on project context.

   This is basically dead code, and untested.

See merge request nexedi/slapos.core!328

Also migrate Computer Partition to Compute Partition

Keep permissions on the computer module to allow computer_module/Base_getComputerToken call

libslap must continue to use the same class names for compatibility.

Changes are made to keep the migration as simple as possible:
  * do not change the catalog table/column names
  * do not change the local_role's names and the related categories
  * keep Computer Consumption portal type
  * keep portal_id's group name
  * keep SLA compatibility
  * keep SlapTool compatibility

SlapTool: restore compatibility with Hosting Subscription method

   The property changed into a List rather them a string

  Even if the Map had no markers, display some location meaningful instead a point into the occean

  Since we use latitude/longitude, "Region" is irrelelant.

Use correct script.

  Contributed by Romain Courteud

  When upgrade the site, we shouldn't revert the count, else it may lead to duplicated values.

slapos_cloud: fixup be0d00d6

Half commited propertysheets change

   This fixup mostly the status column and introduces type (since it is multiple type entry).

    The uid is kept the same so updateRelatedContent don't need to reindex the related object in this specific case.

   This save us double indexation activities triggerred on different moments.

With recursive instances, it was possible that the slapos.cfg introduce a
kind of loop and this was checking again and again the same folders.

Fix this by keeping track of the visited instance root and not visit the
same instance root twice.

See merge request nexedi/slapos.core!327

See merge request nexedi/slapos.core!326

This test was using time.strftime which uses the current machine timezone,
but collection is done in UTC timezone, so the test was sometimes failing
because the strftime('%Y-%m-%d') was another day than the same time in
UTC time zone.

This test https://erp5js.nexedi.net/#/test_result_module/20210811-96D6B55F/8
for example had the problem. By using faketime and TZ=Europe/Paris
environment variable, the same problems reproduced locally 100% of times.

The fix is to always use datetime.utcnow().strftime('%Y-%m-%d'), to not
depend on the timezone.