Really remove security_uid from roles_and_users table

No need to query the catalog multiple times for every partitions

See merge request nexedi/slapos.core!250

scan installed eggs and check if they have known vulnerabilities listed on
https://github.com/pyupio/safety-db

See merge request nexedi/slapos.core!255

cliff complete command only supports bash, but fish offers much more user friendly
completions.

cliff uses a pluggable system, but this where new shell completions can be registered,
but the plugin (CompleteFish) can not access the command manager to get more
details about options, since fish can also show help of suggestion, we want to
access the help of each option to show this during suggestions.
Also we want to make some more clever suggestions (for example slapos node start complete
with services identifiers).
For these reasons we need to register a command to replace the default complete command
and can not achieve this with simply a cliff.formatter.completion entry point.

This can be installed with:

    slapos complete > ~/.bash_completion.d/slapos
    slapos complete --shell fish > ~/.config/fish/completions/slapos.fish

github.com might be not available in many places.

In a scenario of an instance with child instances which does not properly
support destruction, a scenario like this happens:

 1. first report detect that it's destroying a root partition but child
partitions are still started and request destruction of these child instances
 2. child partitions are destroyed
 3. root partition is destroyed

For this case we need to run 3 times

So far implementation of slapos proxy was incomplete regarding partition destructions:
A partition requested as destroyed was properly destroyed "physically", files were
removed from filesystem, services were removed from supervisor, but the partition was
still marked as busy in proxy database, so it was never re-used in subsequent requests.

To solve this, implement the destroyedComputerPartition endpoint to mark the partition
as free.

This is straightworfard for root partitions, but the cases of child partitions was a bit
more tricky, especially because software releases usually does not implement properly
the chain of deletion (it seems this is not properly implemted with softwaretype, only
with switch_softwaretype) and generally because we don't want to leave orpheans partitions.

In the case of ERP5 implementation of SlapOS master we have an alarm which garbage
collect in these cases, so we implement something to reach similar goals. We refuse freeing
a partition while their child paritions are not freed - and we request deletion of these
partitions so that they are deleted on next slapos node report run. Then after a few runs,
the whole partition tree will be completely destroyed and freed, even for software which
does not implement deletion properly.

See merge request nexedi/slapos.core!256

    The user should request to Mantainence to "Open" a contract.

See merge request nexedi/slapos.core!252

See merge request nexedi/slapos.core!254

    - Invoice is generated 15 days before next period and a RR is created
   - 15 later a stop warning is sent (or when invoice expires)
   - 7 days later all instances are stopped if RR still open
    - 5 days after the user is informed his instances will be removed if payment is not done
    - 10 days after ALL his instances will be removed (for safety, as instances can be scaled faster if needed)

So, we assume:

   User is informed 22 days in advance before his instances stop to work, and if nothing is done 15 after (or 37 days after the first request to pay), we just remove all.

Person_checkToCreateRegularisationRequest

slapos_jio,slapos_erp5: move WebSection_getHostingJSPrecacheManifestList from slapos_hal_json_style to slapos_base portal_skins

this script is needed to generate translation data so it must be in a
directory available in all skin selections

See merge request !248

    This email is already part of Subscription System. Regularisation Request is only for later payments.

By following feature of JSON Schema Draft-06 render a structure like:

  "element": {
    "oneOf": [
      {
        "const": "value1",
        "title": "Description1"
      },
      {
        "const": "value2",
        "title": "Description2"
      }
    ]
  }

To:

  <select size="1">
    <option value=""></option>
    <option value="value1">Description1</option>
    <option value="value2">Description2</option>
  </select>

JSON Schema types array and object are stringified to be safely represented
as option keys.