Mostly make it more reliable against slowliness and particular corner cases (slow indexation, data formating)

/reviewed-on nexedi/slapos.core!115

Stop date is used to determinate until when the Acknowledgement will be displayed.

The order of execution of activities are not linear anymore, so this require ensure objects are indexed to be found by the alarm.

Monitoring and Upgrade scope of a Slave handled by the owner of the Software Instance where the Slave is allocated into.

This will require to the user input title, else the form will indicate that information is missing.

Reorder the field to fit better the screen.

/reviewed-on nexedi/slapos.core!114

This document can be used as a real user in some ERP5 instances

It makes easy to trace accounting if we can easily find the Open Order Line

slapos_subscription_request: Add Action to jump from Hosting Subscription to related Subscription Request

This helps to export notification messages from production and place it on a Business Template

   This will allow good rendering by the TestResultLine_view

slapos_subscription_request: Force some tests to runs first to not get disturbed by simulate decorator

  Invoke tic() to flush the activities before run the test

  This helps if you are using runUnitTest --save/load --update_only=bt5_name

  The afterSetup modifies the certificate_authority_path in order to allow us to
  do parallel tests, invoke fixConsistency restore the original value expected
  and set by the configurator.

Simplify the alarm call to not re-query more them once.

This prevent launch activities for all objects in the list.

The amount of disable should be too small, so no need to worry so much here.

Archive Open Orders which contains no lines, there is no reason to keep a user active if he has no Hosting subscription

Don't set new stop dates smaller them the ones currently set. If the value is set for 3 months, we wait until that period come. This affects HS related to Subscription Requests, that required 3 months payment up front.

  If we do otherwise, and if the timestamp is propagated (send in another request), there is a chain of infinity
  recursive bangs

Label is hidden behind the panel.

Only consider slapos user who has at least one instance.