I set that to try to be independent from user config files/environment
variables, but that was a bad idea and not needed (I did that to
investigate an issue I had with jedi, but it was not depending on
environment variables - it was depending on the presence of a
buildout.cfg in current directory)

json was not formatted with `./format-json` this was causing test
failures.

The main change is a new and unique way to override parameters depending on where these parameters are used:
- for NEO, the goal is to avoid a huge `node_list` value (in particular with MyRocks settings), whereas most of the time all values in the list are the same
- for ERP5, we need a way to define different ZODB cache settings depending on the zope id (e.g. huge cache for some specialized zopes, a small cache for the validation node, etc. whereas currently a huge cache for all nodes would waste a lot of RAM)

For any `key=value` parameter that can be overridden, overriding is done as follows:
- `key` defines the default value (not required if the SR already defines one)
- `key!=[[pattern, value],...]`: the SR takes the value of the first 2-tuple whose *some reference* matches the pattern

For NEO:
- new `node_count` and `node` parameters
- `node!` can be used to override `node`: the *reference* is the partition reference (`node-<i>` for standalone NEO, and `neo-<i>` for ERP5)
- `node_list` is deprecated (if still passed, the new parameters must not be present)

For ERP5 ZODB settings, parameters can be overridden at both:
- zodb level (e.g. `pool-size`, `cache-size`... oh, I've just discovered there exists `cache-size-bytes`)
- storage level (e.g. `compress`, `cache-size`, etc. in the case of NEO)

Here, the *reference* is the zope id (e.g. `actitivies-0`)

The `pattern` is a Python regex that must match the whole reference.

Another not-so-small change is that the schema is fixed to only require NEO `cluster` parameter when instanciating a standalone NEO.

And a few fixes.

/reviewed-on nexedi/slapos!661

Some eggs to provide "intelliense" for python withing ERP5

/reviewed-on !649

Commit d0df63cf broke support for SQLite.

Currently, NEO-STRESS often fails because it is assigned
on the same test node as other test suites that:
- overload the test node;
- are often triggered at the same time.

The original work for [monitor to plugin migration](!614) missed
important parts of resilient stack implementation due to lack of SlapOS
Profile Integration test coverage for those cases.

/reviewed-on !659

When the image is a block device, the guest must also run Linux >= 5.0.

BT were moved into bt5/ subdirectory in
nexedi/erp5-doc@3996ae1f

Unfortunately pbs recipe is just simply creating an executable to check own
state, so keep the etc/promise directory in the partition for now, as it is
supported by monitoring checks.

This reverts commit dcd2f8d6.

It has to be redone with proper test coverage.

This reverts commit 04ea0535.

It has to be redone with proper test coverage.

Since the introduction of shared parts, there is no guarantee about
the location of sqlite3 binary.

Calling makeModuleSetUpAndTestCaseClass results already with preparing some
environment and also test classes will run the promises, so they would never
execute test_kvm_sanity_check.

So create a method sanityCheck to check the environment and depending of the
result call or not makeModuleSetUpAndTestCaseClass and skipIf test cases
when environment is not sane enough.