Show *_info in highlight way, this permit user "share" documentation and messages for the users (ie.: Link to documentation or Tutorial)

- Show float with 2 digits after . only
- Don't list reversal Sale Transaction Invoices, this only leads to confusion
- Show Payment State as Cancelled if a Reversal Sale Invoice Transaction is started for the Pending account (it means Payment was cancelled).

- List Invoices in Reverse Order (start date), so it is easy to identify if you have something pending to Pay.

If Sale Invoice Transaction is created for account validation (Causality == Cloud Contract), skip this Consistency Script to check prices against Sale Packing List

This rule is used when a Sale Transaction is generated without packing lists. (ie.: Account Validation Case)

Set Computer/Software Instance owner on the support requests, so owner can take a decision.

Add a new "Cloud Contract" document per user.
If the contract is validated, allow instance allocation.

Automatic contract approval is done if user already paid an invoice.
A validation invoice is automatically created if the user has no invoice.

Remove early optimization.

Just to trigger tests.

  This implementation is not optimal from performance point of view,
  however the fix is more urgent and the current implementation has
  nearly the same performance outcome.

  Optimisation should come later on query less objects per time.

Increase revision of BT.

Also return created objects for _createComputer.

getUrlString will be used to link the Computer to a External Inventory and/or Documentation System.

  Don't show close computers on rest API when list, it is not relevant for monitoring
  Don't list request_destroyed software instances or looking for partition, as it is not
    relevent for monitoring.

Refactor and rename RSS Listbox implemented for Support Request
Include RSS action on Regularisation Module

Those fields are not used anymore.

Only generate a limited number of Support Requests per time (For now hardcoded in 3).
Drop duplicated cases when computer is not contacting already.
Don't generate SR for recently created instances.

an absolute mock module is already used.

This is duplicated check with "Check if Computer Contacted". The only ocasion that this can happens is if someone comments "slapos node instance" from cron (in this case is not master duty to know if backend is not modified in a bad way).

This is a login feature (experimental and prototype) which permit login on SlapOS master using external logins (google, facebook, ...) accessing a url. SlapOS master works  on this case as bridge only, for setup cookies on master domain to permit usage o of external websites later.