Merge branch 'instance_python_promises' of https://lab.nexedi.com/xavier_thompson/slapos.core into wip/rc

this is part of libc

Merge remote-tracking branches 'origin/master' and 'origin/feat/cli_request_file' into fix/checkSoftware_so

Thanks to more specific exceptions the caller is able to understand what
exactly happened during processing, especially useful in case of the caller
uses testcase, and can sneak into real problems during setUpClass.

fnmatch.fnmatch signature is path, pattern, we were passing arguments in
reverse order, so effectively we were only checking executable files.
Several .so are executable, so we were checking many .so anyway.

Some advanced tests setting up clusters need to being able to come in half of
the setup process to do some actions on the cluster in order to have its setup
finished, thus allow to override extracted _setUpClass and separated
waitForInstance, so that those actions can be executed.

The SLAPOS_TEST_SKIP_SOFTWARE_REBUILD changes the default to rebuild always
the software by setting install_all to true.

The SLAPOS_TEST_SKIP_SOFTWARE_CHECK allow to skip software checks, if not
wanted by the developer.

Forgot to update the test.
See nexedi/slapos.core@3ceef26a

Client uses Person_requestComputer, so, allow this script on the compute node token

See merge request nexedi/slapos.core!335

When --only-cp is provided, iterate over a filtered partition list
instead of repeatedly checking at each iteration if the current
partition is in the --only-cp list.

   This was done by Thomas, I'm just pushing it into git

    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.

See merge request !333

this fixes 86ce8b8e which had an error
the current_output variable was not reset when the current output ended
in \n.

As a result, logged output was sometimes containing some parts of the
program output twice. We could even catch it in unit test, when running
the test multiple times. It also happened on test node with
https://erp5js.nexedi.net/#/test_result_module/20210826-1706D7F50/10

The is trivial, we reset the current output also in this case. The test
suite is extended a bit, with added tests and test adjustments made during
the debugging. With test_exec_large_output_multiline the problem triggers
almost every time.

   This is basically dead code, and untested.

See merge request !328