This makes easy write or update tests per workflow-basis

    Drop an duplication, probably came from copy and paste

   Introduce API on person to handle the requests of Organisations and
Sites.

   This aims to transform *_createMovement into an proper API to handle location/project/owners transfers between Sites/Project/Organisations.

    This allows the project owner leave the project if he would like too

  This API aims to handle token generation for person, rather them
  keep ad-hoc API on scripts for specific usage

  Acquire listbox configuration from erp5 using proper API rather
  them hardcode the values over the .js

   - Include person.requestProject API on person_slap_interface_workflow
   - Include project_slap_interface_workflow on Projects

For fish shell, make slapos node software --only-sr and slapos node instance
--only-cp complete the software and partitions from the local slap proxy

We don't use abbreviations in the user interface, this also makes
another message to translate.

This reverts commit a8f83ef9 and the
other places where this pattern was copied.

If some non verified connection is being made, let's be honest and don't
hide it to user.

In the commit dc559dad specific exceptions
has been exposed to caller, but in case of SLAPOS_TEST_DEBUG enabled unusal
exception is raised.

This commit improves the situation so that behaviour is consistent neverthless
the SLAPOS_TEST_DEBUG.

This reverts commit 71fd0fab.

All Zelenium tests are failing because of this change.
Revert until all tests are fixed.

The change was missing in the commit 439786ba.

Filling the service worker is not supposed to take so much time

The inventory catalog uses second for precision.
Ensure all test movements are created in different seconds.

See merge request nexedi/slapos.core!334

The state of Software Release being cleaned up or not is really never
known, so simply drop the concept.

Use case to cover, is some developer having upgrade_scope=auto set and
installing archived SRs - it IS expected that such SR would be cleaned
if not used.

The allocation_scope of Compute Node is as important, as Compute Node
owner regarding the software management itself.

Add a test where the binary is compatible but the signature is unverified

Avoid catching interruptions and system calls during exception handling

Get all binaries for the requested SR
Indicate which are verified by the certificate list

Leave string interpolation to the logging method

Use `gcc -dumpmachine` instead of `platform.machine()` to discriminate
architecture

Use libnetworkcache to list only binaries with verified signature