slapos_erp5: wip security for bulletin

slapos_erp5: Site Message are visible to all project's customers

slapos_erp5: Note will only be visible to project managers

slapos_erp5: Acknowledgement will only be visible by customer

slapos_erp5: trigger Bulletin local roles calculation

slapos_erp5: set bulletin module business_application

slapos_erp5: coding style: add bulletin scripts

slapos_erp5: coding style: skin selection: erp5_bulletin

slapos_erp5: drop dependency

slapos_panel: allow created different kind of Event

slapos_panel: action to add a Bulletin

slapos_panel: display Bulletin in the ticket's listboxes

slapos_panel: view Bulletin / Site Message

slapos_panel: create Note event for Bulletin

Keep the event only visible to managers

slapos_panel: change the Bulletin's event portal type based on the context

slapos_panel: dont add attachment to bulletin

It will explode size of acknowledgements

slapos_panel: don't expect any custom resource for Bulletin

slapos_panel: missing bulletin dependency

slapos_panel: drop dependency

slapos_crm: wip bulletin idea

slapos_crm: fixup bulletin?

slapos_crm: fixup

slapos_crm: add erp5_bulletin dependency

slapos_configurator: test configurator: bulletin_module

test: erp5_bulletin bt5 added

test mixin: erp5_bulletin

This reverts commit 74607091.

slapos_erp5: production users can create invitation token

slapos_erp5: do not allow creating Contract Invitation Token anymore

slapos_erp5: invitation token roles

slapos_erp5: trigger invitation token local role generation

slapos_erp5: is an Invitation Token a ticket?

slapos_erp5: test invitation token roles

slapos_erp5: roles for Assignment Request

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

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.

requestStart seems to be called on every instance every day.
There is no need to call the alarm if nothing changed on the instance

slapos_cloud: allow recreating a Compute Node even if there is an invalidated node with the same title