Shared parts can be detected by presence of .shared file or presence of any
shared_part_list paths in .installed.cfg, and in such case do not allow to
upload to binary cache.

It's better than checking presence of shared_part_list in the configuration,
as this does not give real information if the shared technique was using
during installing given release.

This adapts 19e3f1b6 to 5cbd70bc

   This is a port of the code from slapos.toolbox for future
   replacement.

/reviewed-on nexedi/slapos.core!150

This operation is done by the instance itself, updating the timestamp
here will create an infinity call, where the instance is always edited
and it is forced to run.

  At the ERP5 implementation of slapos master this api don't modify the
timestamp (which is not defined by modification date but by an specific
 workflow.

/cc @jerome

/reviewed-on nexedi/slapos.core!151

Now that slapos node instance outputs summary of problems, no need to
pollute the logs so much

This will improve the summary of problems at the end of slapos node
instance.

/reviewed-on nexedi/slapos.core!144

[Test result](https://nexedijs.erp5.net/#/test_result_module?extended_search=%20%22Boxiang-SLAPOS-CORE-FIXUP%22&page=form&view=view)

/reviewed-on nexedi/slapos.core!149

Used to remove shared parts that are no longer referenced.

With shared part installed for example in `/opt/slapgrd/shared/name/HASH`
the heuristic is to assume that if `HASH` is present in a software's
`.installed.cfg`, then this software is using this shared part.
Similar, if `HASH` is present in
`/opt/slapgrid/shared/another/ANOTHER_HASH/.slapos*signature` then share
part another for hash `ANOTHER_HASH` is using the shared part.

This also have some support to recursively look in instances and if they
contain a `slapos.cfg` file, look for software and shared parts to see if
they use the shared part.

In other cases, this shared part can be deleted.

/reviewed-on nexedi/slapos.core!139

python3-wheels and python3-setuptools are installed when we installed
python3-pip only if recommended packages are installed. It's better to
force the installation of what we need.

  This normalizes the result on python2 and python3, and as well, makes the
  result more accurate.

When reinstalling a computer, 'node software' may run before
'node format' has created users, then it fails because it can't set
ownership of the directory it created. The directory already exists
on next runs and before this commit, it didn't fix the ownership.

/reviewed-on nexedi/slapos.core!132

The most important are:
 * sometimes instance was not properly destroyed, apparently we need to retry `slapos node report`
 * if instance is not properly destroy, remove the files ourself and mark test failed
 * we need to see log files and config files from the instance

there's also a few small commits not directly related.

/reviewed-on nexedi/slapos.core!145

/reviewed-on !143

  Introduce a new command for run promises only, from all partitions. This helps to perform quick
  checks.

  On the tests for ConsumptionReportBase, it contains a port from a test
   on slapos.toolbox done by Alain Takoudjou.

  This may case more memory usage and more 'live' data to handle,
  for this reason, I'm making it configurable

  This new report class is responsable for generate a file (serealising it per pertition),
  instead rely on concurrent calls to the sqlite.

  This is just to clean the methods a bit

  Extend monitor to grab this information, this allow us use slapos node collect more efficiently, and
  prevent others softwares to access directly the database.

- We should only try to remove leaked partitions if we detected some,
  otherwise it may produce a strange message "unable to delete leaked
  partitions".
- If some supervisor configuration is still present after partition
  deletion, they must be removed not to block next test and the current
  test must be marked failed.

destroying instance is supposed to remove these, but when there are
issues removing instances we sometimes have supervisor config left from
previous instances.

Reformating now delete theses after logging the problem.

Quite often when test fail we don't have any information about what was
wrong with the tested instance. Dumping the generated etc/* files and
the instance log files should help diagnosing such errors.

/reviewed-on nexedi/slapos.core!147

This command sometimes fail, for example with:

  2019-10-23 06:10:56 slapos[27556] ERROR
  Traceback (most recent call last):
    File "slapos/grid/SlapObject.py", line 800, in destroy
      self.cleanupFolder(self.instance_path)
    File "slapos/grid/SlapObject.py", line 836, in cleanupFolder
      os.remove(os.path.join(folder_path, file))
  FileNotFoundError: [Errno 2] No such file or directory: 'tmp/inst/defp5/.installed.cfg.tmp'

otherwise logged error and critical messages are just ignored.