The upgrade decision portal type should be return whenever getPortalTicketTypeList() is called.

   This aims to fix Worklists for Events when they follow up to an Upgrade Decision.

   On final state, we just deliver all stopped events related to Subscription Requests.

   While the Subscription is submitted, the events will be kept stopped,
   so the manager (accountant/sale) can have it on their worklists.

   Add tests for new alarm

   Invoke alarm to deliver related events, whenever the Susbscription
   Request is invalidated (end of life).

   Rename *[sS]toppedEventToDeliver to *[sS]toppedEventFromSupportRequestToDeliver to reflect proper usage
   Add *[sS]toppedFromEventRegularisationRequestToDeliver to handle delivering of Events from Regularisation Request via new alarm
   Update and add tests accordingly.
   Narrow the slapos_crm_interaction_workflow to only trigger alarm if the follow up portal type is relevant, to not over trigger the alarm on excessive amount of occasions.

   On final state, there is nothing that could be done, and send a message won't be seen on worklists anyway.

    Only [Accounting|Sale] Manager can validate the ticket (interrupting the process)
    [Accounting|Sale] [Agent|Manager] can suspend the ticket (continuing the process)

   It differs from Support Request (no recheck no project..)

   The Regularisation Request columns differ from Support Request now, since it has no re-check or project.

   Since Regularisation Request is created by lack of payment, usually the accountant is the one that can reply about ways of payments, and the one that can include manual payment (ie.: Wired transfer).

   Future possible use cases (Regularisation Request for Org?) would require accountant help to handle payments.

   Update related tests.

   Accounting Agent is assignee (like sales agent)
   Accounting Manager is assignor (Like sales manager)

   Only Assignor can re-open (pause) the process to destroy unpaid instances.

slapos_crm: create monitoring Support Request for Slave Instances in error, and instances on a Remote Node

Detect url/type changes which are not compatible with the remote project.

See merge request nexedi/slapos.core!696

This will support buildout extension to download from gitlab API with
authentication.

The code has already been refactored a bit to be able to pass a
download instance to SoftwareReleaseSchema, for now to instanciate only
one Download but in the future this might be extended to pass some
configuration to the Download instance.

The performance was much worse.

Workflow state was not the correct one.

See nexedi/slapos.core@76edda30

This partially reverts commit 14c39681.

There is no need for custom the actions, as on slapos_panel fast input is
used instead.

Keep for now the older state name for ensure consistency with the current
usage.

   This was replaced on the panel so, no need to have it on workflow action. This may reduce the delta on the workflow itself.

   For sure, we won't calculate worklist from this form

    This workflow isn't used any more since the re-implementation.

   This prevents produce inconsistent objects whenever system evolve.

  New string to translate
  int to bool change on XML

  DeprecationWarning: <Workflow at instance_slap_interface_workflow>: Script calling Instance_checkConsistency instead of script_Instance_checkConsistency

   Provide all common options as a method, so it is easy to understand security.

moved from erp5 SR test suite

See merge request nexedi/slapos.core!705

adjusted to use findFreeTCPPortRange and fix typing / formatting errors

  Ensure to convert the text values to a safer output that will be compatible with XML 1.0.
  See: https://www.w3.org/TR/REC-xml/#NT-Char

   Try to guarantee that data is consistent and wont fail later on
   while been converted to XML with special attention to non-XML
   compatibles characters, like backspace.

   Include constraint to ensure title is XML compatible on Software
   Instance, Instance Tree and Slave Instance. (Not required for Compute
   Node as far as I checked).

   Copy text_content (parameter), sla_xml constraints from
   Software Instance to Instance Tree and Slave Instance.

   Copy connection_xml constraint from Software to Slave Instance for
   consistency.

   Add more tests to ensure that an Instance cannot be created if data
   is invalid, or not XML compatible.

   Add utility scripts to validate XML and XML Marshaller compatibility