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.

   Update of state should be done by alarms according to current implementation.

   Whenever you post a ticket on a suspended Regularisation Request it interrupts the triggers and nothing is removed, until it is suspended again.

   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.

  it cause confusion on grep and search, if we need access its code,
  we may rely on https://lab.nexedi.com/nexedi/slapos.core/-/tree/master/master/bt5/slapos_jio

  This helps to emulate payments, so we can test outcome before/after payment to wechat

  Only launch caucase when needed.  Not all tests need
  caucase, this saves a bit the overhead to run it

The performance was much worse.

Workflow state was not the correct one.

See 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 !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

This is a fixup of 3194cc75.

slapos_crm/panel: rename Project_createSupportRequestWithCausality to Project_createTicketWithCausality

Prepare support for new ticket portal types.

User is not visible in the panel.

It should reduce number of open order expand calls.