This can happen when the user "opens a software releases" for the first
time : in that case an instance is requested by the runner for this
software release, but the SR is not buit yet (only requested)

For exemple we don't want to switch an instance to a software release
that is marked as to-be-deleted

as no data is changed/created server side

in the field listing the software releases available for the instance.

Which doesn't save the "software.cfg" extension in the .project file,
as it is done in current webrunners

Creates a new view with a more fitting name, replacing an older one.
Also, requesting instance should happen only if there is no current
instance, otherwise it may erase data.

   The generation of the link and the verification were inconsistent, this commit
   normalize both.

   PS.: Software Links are deprecated, it should be removed in future, as it lost
   the goals

While adding the support in "promise: Support ssl_certificate in
check_surykatka_json" coverage for error reporting was missing, which has been
extended in this fix.

/reviewed-on nexedi/slapos.toolbox!78

This is another fixup for commit
1c8269b2.

This will lead to minimise amount of entries, and they will be only shown
when the status would change.

Improvements:

 * total_seconds from surykatka is parsed
 * failure-amount is configurable
 * various smaller bugfixes

/reviewed-on nexedi/slapos.toolbox!77

Result of the promise is not important for instantiation.

Sites with bad certificates are reported with null values in surykatka
output, thus they have to be handled correctly.

It means that the server didn't reply at all.

Show URL only once and having this in mind simplify messages still keeping
all information.

It is only checked when maximum-elapsed-time is passed and surykatka is
recent enough to report total_seconds.

Also improve reporting even more to provide readable information for those
massive promises with ERROR/OK mixed states.