Compute Node must be able to invalidate Certificate Login whenever the Software Instance is destroyed.

   Since login is invalidated the user wont be able to login into master anymore.

   Revoke certificate too often may cause an excessive amount which dont scale.

See merge request nexedi/slapos.core!540

   This is covered by UI test

    This ensure that when users access the site, the information is likely to be cached already.

  Dont fetch the list twice for Network and Organisation
  We dont use Project anymore
  Direct call API for getAccessStatus instead call ComputeNode_getNewsDict

  Similar to getComputeNodeInformation, use caching system to not
  recalculate status for the related software instances, only acquire
  from cache if it is updated.

  There isn't a need for such aggregated monitoring on Project

See merge request nexedi/slapos.core!546

    This is mostly covered by UI tests

See merge request nexedi/slapos.core!545

See merge request nexedi/slapos.core!543

See merge request nexedi/slapos.core!542

  There are really slow servers running tests, if they fail it cause way too many false positives.

  On a distributed tests environment, it is OK, since the fast servers may pick all the tests anyway,
  causing a bad node be ignored.

  Non owners cannot transfer the objects across different projects.

  It is safe to ignore if value is none (it indicates the user sent a raw data).

See merge request nexedi/slapos.core!515

See merge request nexedi/slapos.core!541

  Priority is set to avoid large accumulation of activities to be queued.

Use the format return code to distinguish between failure to format or
failure to report to master at the end. Then make boot run format even
if the master is unreachable, and:
* if format fails to report, wait until master is reachable, and retry
* if format fails for another reason, retry after a fixed 15s delay
* once format succeeds fully, bang

See merge request !537

   Invoke extra expected steps, commonly used during upgrade via activities to accelerate the administrator actions while upgrading.

See merge request !536

See merge request !534

   The transfer is processed later, so the value wont appear right the way after proceed.

   .... unset require where it isn't needed.