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

Stop and delete b2b services

- Support Slave Instance allocated in the same tree
- allow creating allocation consistency ticket on Instance Node
- handle allocation consistency for Slave Instance without Instance Node

This is a fixup of d42de18b.

history and statistics files are sometimes corrupted because of invalid json

We do 2 things to improve this:
 1. we use json.load to read the previous file (this will detect if the file is corrupted)
 2. we use json.dump to write the entire file at once in a temporary file and then we move this file to be atomic.

Probably this will consume more resources.

See merge request !728

  This prevents installation update modification date due Web Page
  modification date is newer.

  This fixes the coding style tests broken by:

    slapos_web_deploy: Added missing standalone-test
    slapos_web_deploy: Add rplc_coupler deploy script

  It was create a while ago, but never pushed.

Do not acquire from Person to an Organisation, as most user do not have access to the organisation_module

- directly show the software_release and sofware_type informations
- instance title is meaningless on this view, as admin want to get an understanding of which kind of software are instanciated
- drop creation_date, image columns

See merge request nexedi/slapos.core!727

copy netrc file to software home location with the good ownership.

slapos_erp5&cloud: Reimplement (and speed up) security to use ERP5User_getUserSecurityCategoryValueList

 No need external script for this.

 This change introduces a test change on testSlapOSCloudShadow, that
 include R-COMPUTER and R-INSTANCE for shadow users.

 After check, this feature (shadow) is not used for compute node or
 software instance users, so despite it is not needed (introduced 12yr
 ago), I kept just for reference.

 If those tests eventually break or cause problem, it is safe to remove
 them later on.

  Include a custom ERP5Type_asSecurityGroupIdSet, since we need to handle
  the order of source_project + function (sort) a non-standard way.

See merge request nexedi/slapos.core!721

This way, running `slapos request n https://software.url` does not emit
logs when fetching the software schema, but it does when using the
`--verbose` flag.

Tests were using mywebsite.me, which is an existing domain for which
HTTP requests timeout, this make the test slow and it is generally not OK
that the test use a real web site. Using .example, as recommended by rfc2606
prevent these problems.

  Move shared code into InstanceTree_getNodeAndAllocationSupplyCellList
  and reuse into CRM and PDM for get the related Allocation Supply.

  This preserve the logic into a single location.

  Include more tests and extend implementation to now support Instance
  Node too.