it cause confusion on grep and search, if we need access its code,
  we may rely on some older tag to search the related code

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

    Add a daily alarm to verify if all instance allocated have proper Allocation Supply configured and if they
    still respect the SLA.

    Extend SoftwareInstance_getReportedErrorDict to verify SLA, since, in general the context of the report should be the instance tree. The calculation is cheap to assert the SLA, and this script already has specific checks to inform the user about bad approaches.

Do not check deleted root instances