Prefer use payment page related to the instance tree rather them the generic one, so it reduces confusion.

   Introduce a listbox rather them a page template or HTML for a more
   future-proof approach.

   Some logic could be generalized for shorten the test/get scripts,
   but for now it is better keep them as is.

  The alarm should update the state of Subscription Request whenever Compute Node and Project are invalidated, to proper cancel it as soon as possible.

   The cancellation and validation occur on the same group of objects, so to save code and processing merge both.

   "Cancel" takes precedence over "validate", if the user destroys his instance "too fast" we should not drop his subscription request as soon as possible.

  This helps to preserve backward compatibility with existing sites, that would have broken documents by the absence of the portal types.

  This was causing bt5 to generate delta while export.

  Merge the delta, minimizing the diff on the fork of the file.

  Currently, it is not used on general code. Since it is not used
  we are dropping from our codebase. Nothing prevents other projects
  include it in future.

See merge request nexedi/slapos.core!639

- do not return url if connection parameters are not available
- use byteify instead of encode to handle dict json data
- drop obsolete setting_configurator url
- drop json loads/dumps
- set slapos master url parameter

   Whenever an Instance Tree is destroyed (and archived), cancel the Subscription Request
   on Submitted state.

    This is required since the Submitted Subscription Requests count as required Deposit, and
    the user clearly didnt conclude his payment.

   Similar to "Pay" Section, it will display the outstanding amount right the way to pay. This allows the user "immediately" have their instance ready to allocate (validated) and it wont require to navigate to pay section or subscription request.

   This allows the script been used with normal user security roles,
   since only account_module is cause restrict access (by the current
   usage).

   destination section can be an organisation, so use shadow to avoid
   relax security.

   Display if the instance is payable (price currency/unit)
   Create and redirect to deposit payment if balance would require a deposit to the instance to work.

  This allows to to getPrice before actual create a subscription request.

* add 'Add Event' action on the panel
* display discussion on the upgrade decision

Allow to upload an attachment when creating an ticket's event.

The text_content parameter is limited to text/plain.
More work is required to support text/html content_type.