It is mostly broken and nobody keeps the tab open waiting for update. if someone wants real time, it is better to use monitoring app

See merge request nexedi/slapos.core!570

  "disabled" is not actually used anywhere (even on tests), never is already set everywhere.

Slapgrid object makes a connection to master node immediately,
thus if you create a slapgrid object without checking pidfile and if
master node responds very slowly, you may get tons of stucked slapgrid
processes by cron and system may become unusable.

See merge request nexedi/slapos.core!560

Factor test partitions formatting into a separate method to facilitate
customising the formating step in tests that need to do so.

Now that `StandaloneSlapOS.format` calls `slapos node format`, remove
redundant operations in `StandaloneSlapOS.format`, such as updating
the slapproxy.

Always put IPv4 before IPv6 in partition address list, because that's
the existing order and some things rely on that order, such as tests.

A nice example of Hyrum's law in effect.

See merge request nexedi/slapos.core!566

   Destination Reference wasn't used
   Display "Request By", this makes easy to identity if this is a loose instance

   This makes navigation easier.

   It helps to know who requested the instance

See merge request nexedi/slapos.core!558

    Just invalidate the certificate login

    This drops certificate revocation, it only requires to invalidate the Certificate Login to make login invalid.

   revoke occur directly on the Certificate Login

   Other users wont have permission to cancel valid Certificate Logins, only Compute Node owners.

  Now we dont rely on the document reference anymore.
  Invoke generateCertificate on tests else the user isnt valid.
  Note:  Login name returns the Certificate Login reference, to keep
    backward compatibility with the API (and current usage) it user
    the actual user reference, so it is easier to identify which document
    set the access status.

   This issues SSL Certificates and use Certificate Login, rather them require to revoke it.

See merge request !503

   By using getModificationDate, it ensures that the data is set according to the transaction, since catalog can be updated since the transaction started leading to a recent etag using outdated cache from the transaction.

See merge request !559