Use *_getReportedErrorDict for fetch the error message, avoiding duplicate the code/logic on multiple locations
   Drop batch_mode on *_getReportedErrorDict  since it is not required.

   The goal here is:
       - Only check projects that have (at least one) monitored computers
       - Only check Instance Trees that have  (at least one) instance

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

   Keep in mind that in the future, we can use "close for termination" in addition to close forever to create tickets when a computer is going to be removed, so the administrator or user can take actions in relation to it.

   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

    Merge into Project_checkMonitoring for launch per-project basis.

   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.

   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 action and forms that were not used anymore (and it was not exactly working).

 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.

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

   Old script not used anywhere

  Under refactoring...

  it cause confusion on grep and search, if we need access its code,
  we may rely on https://lab.nexedi.com/nexedi/slapos.core/-/tree/master/master/bt5/slapos_jio

  This helps to emulate payments, so we can test outcome before/after payment to wechat

  Only launch caucase when needed.  Not all tests need
  caucase, this saves a bit the overhead to run it

  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

without the option --ignore-installed (even with
PIP_BREAK_SYSTEM_PACKAGES=1), pip3 upgrade on Ubuntu 24.04 would report:

Requirement already satisfied: pip in /usr/lib/python3/dist-packages (24.0)
Collecting pip
  Using cached pip-24.2-py3-none-any.whl.metadata (3.6 kB)
Using cached pip-24.2-py3-none-any.whl (1.8 MB)
Installing collected packages: pip
  Attempting uninstall: pip
    Found existing installation: pip 24.0
ERROR: Cannot uninstall pip 24.0, RECORD file not found. Hint: The package was installed by debian.

   This is for backward compatibility.