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.

    We index now for very few portal types the bool(checkConsistency()) in order to search inconsistent documents.

    The indexation is limited to the scope we must monitor rather them all documents for 2 major reasons:

        - Too much useless constrants on erp5 code base, not applicable for our project (ie.: On person)
        - Performance on indexation is penalized from this extra cost, specially when index large trees (Deliveries or open orders)**

    ** Not so much, however, on a scale of millions of documents it can make a major difference, so this commits keeps up to the minimal implementation.

   If partition is None, it means the computer was reformated and there is garbage on it. It is meaningless to process this.

The `local-software-release-url` option allows migrating the software
URLs which are local paths by rebasing them on the path provided by
the option.

Do not migrate software release URLs if the old root path and the
new root path are subpaths or superpaths one of the other.

In addition, do not migrate an URL if the old one refers to an
existing file and the new one doesn't.

Also, create a backup of the database before migrating.

See merge request nexedi/slapos.core!338

  Since we an introduce more roles on project specific scope, like payroll and more general acccounting,
  use mixing for this allow us to extend it on Project specific mixin.

This is a fixup for 5c938a8d.

this is part of libc

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.

In old Debian 10, after the release of Debian 11, apt update is failing
like this if we don't add the option "--allow-releaseinfo-change":

root@debian:~# apt update
Get:1 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Get:2 http://http.us.debian.org/debian buster InRelease [122 kB]
E: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

Normally, all compute node are validated.

It allows to have a faster sorting.

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.

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

   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 nexedi/slapos.core!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