For now the system allows allocate with instance_guid on remote, so it is not good
  to check

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

  Now we rely on implementer decorator

   Base_addSlapOSSupportRequest always created a ticket so no reason to invoke Project_createTicketWithCausality anyway.

Floating point arithmetics often lead to unsignificant differences between
expected and computed values (this is the typical example of `0.1 + 0.2 !=
0.3`). Because of this, some tests using `assertEqual` to compare two floats
were failing. The Python method
[`assertAlmostEqual`](https://docs.python.org/2.7/library/unittest.html#unittest
.TestCase.assertAlmostEqual) can prevent these issues by comparing values up to
the seventh decimal place. To find all occurences, two RegExp were ran on all
files of the `tests/` folder: `assertEquals?(\\(.+, [0-9]+\\.[0-9]+\\))` and
`assertEquals?(\\([0-9]+\\.[0-9]+)`.

/cc @xavier_thompson @tomo
/reviewed-by @jerome
/reviewed-on !719

The old `SafeConfigParser` class has been deprecated since Python 3.2, and was
fully dropped in Python 3.11. See issue
[#45173](https://bugs.python.org/issue45173) on Python's bugtracker.

/cc @xavier_thompson who may ping anyone else if needed

slapos_accounting: calculating the outstanding deposit amount need to also check the balance which include the VAT

Test: ensure a second service can be ordered

so that we can click on the link

   If a software instance with 1 or more slave instances allocated on it is destroyed the instances aren't reallocated, so let's create a ticket to high light the problem.

  Probably a copy and paster or typo.

   Destination is never set... Destination Section is a proper value for the condition.

   Whenever the Upgrade Decision arrives at final state (Close, Reject, Cancel) all stopped events are delivered.

   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.