Keep testSlapOSCRMAlarm for regularisation request related alarms
  Create testSlapOSCRMMonitoringAlarm for tests related to Monitoring ticket creations and so on.

    Merge into Project_checkMonitoring for launch per-project basis.

   Refactor the implementation of the alarms:

      - Search from Project rather them query compute nodes, directly
          respecting if the project can create tickets

      - Split ticket creation from messaging introducing
          *_getReportedErrorDict to calculate the error messages
	  (so we can re-use them)

      - Merge 2 alarms (for check compute node and check compute software
          installations) info a single one, so we launch at least half
	  the amount of activities for compute nodes.

      - Drop the specific alarm and to issue a ticket if the user has an
	instance on a 'close/forever' compute node

      - Reimplement SupportRequest_recheckMonitoring

   Merge SoftwareInstallation_getReportedErrorDict into ComputeNode_getReportedErrorDict:

     We only check for problems from Compute Node perspective, so we should
     report only one ticket per time.

     SupportRequest_recheckMonitoring can guarantee that the compute node
     don't have other problems while closing the ticket. So, this reduces
     the scope of checks, for example, if the computer isn't connecting,
     there is no point in check all software installations inside. Another
     example is, if multiple software releases are failing we dont need to
     report each one, since the administrator is informed and create
     multiple tickets for the same compute node will only spam the
     administrator.

   This feature was replaced by "Recheck" Monitoring later on and never used. Since it is broken since the refactoring, it is best to improve "Recheck" and drop this action for good.

   Drop the action and forms that were not used anymore (and it was not exactly working).

   Moved jump from slapos_crm
   Drop tab since this information is duplicated with the jump anyway.

   It is duplicated with Panel View and InstanceTree_view so it provide no benefit in keeping it

   Moving logic to SoftwareInstallation_hasReportedError allow us reuse the logic on SupportRequest_recheckMonitoring script.

   Old script not used anywhere

    Dont use cache to check ticket creation is closed.
    Use countResults to not require len() over the list.

 This reverts commit ae35b7bc.

  Site messages arent used anymore for this purpose, so custom the view
  is not needed, since Site Messages arent used by any UI and
  we dont have plans to use anymore.

2^16 is too big and in many machines, you will have "Argument list too
long" error. Actually 2^16-1 is the limit and with the "echo "
characters in the beginning, we could do max "2^16 - 6". Using 2^15 is
already enough.

getMovementHistoryList may return the same event twice.

erp5_forge is not needed to run the upgrader

connection_value can also be a list.

Interact with the support request if possible.

- Type hints for testcase module are completed.
- Type comments (to be compatible with Python 2) have been added to
  other parts of slapos.core only when necessary to achieve full type
  checking in the testcase module, with Pyright in strict mode.
- Docstrings added/completed for the testcase module.
- Source is formatted with ruff.

See merge request nexedi/slapos.core!693

erp5_interaction_drop/slapos_crm/slapos_cloud: increate priority of alarms checking all documents without changing them

As there is no comment, let's try to drop it.

- change instance tree owner
- change paying organisation (switch b2b)
- change payable to free
- change payable price

It can be used on a submitted Subscription Request or a validate Open Sale Order

slapos_subscription_request: allow to force the trade_condition_type when creating a Subscription Request

User may have created multiple allocation supplies for the same release/type/node

It prevent to change suspended Support Request to open again.

`Path` objects are immediately converted to a string.
This can only be done easily in tests for now, as slapos.core has to
still support Python 2 users in other parts of the code, and `os.fspath`
was added in Python 3.6.

See merge request !686

  If failover textarea is rendered, we ensure that at least the software type is set, in case it exists.

   This prevents bad software.cfg.json break the form while editing some instance.

  In case maileva is used, accountant needs access to system event module for add
  maileva exchanges. This role should be removed once Maileva integration be refactored