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

See merge request !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 !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 nexedi/slapos.core!537

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

See merge request nexedi/slapos.core!536

See merge request nexedi/slapos.core!534

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

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

  Hold the request makes the user hangs there waiting for response.

See merge request nexedi/slapos.core!533

See merge request nexedi/slapos.core!531

   This is a failover approach to prevent the user loose its value if it is not complaint with the field

See merge request nexedi/slapos.core!532