... Unify scripts into Base_getEventList

  In order to use getMovementHistoryList too

   It is used to get the events that follow up to a ticket that aggregates (or sub object aggregates) to an document (usually Compute Node or Instance Tree).

   Reuse Base_getOpenRelatedTicketList to query tickets consistently and extends original goal to also show Upgrade Decisions.

   This tab shows all Tickets related to the computer and to all instance trees that has one instance allocated on it (even if isn't the one that is failing).

   Use default_or_child_aggregate_uid is enough (and simpler).
   Use specific states to be consistent with RSS queries.

   Reduce the number of scripts and refactor the query script to rely on getMovementHistory.

   Before only the latest event was notified, to reduce the list and only to ping the user to access the site. Now all events are considered on the list (not the latest ones) and include some general clean up on base RSS feeds.

See merge request nexedi/slapos.core!423

See merge request nexedi/slapos.core!429

   Events are creates via script (and API) now, instead jio_post.

Add `README.md` instructions explaining how to adapt the migration
tests after upgrading the proxy database version.

When migrating entries, use `INSERT OR REPLACE` to get rid of duplicate
rows that cause constraint violations, instead of raising an exception.

Note that this only affects the `forwarded_partition_request` table:
for other tables it changes nothing in terms of behavior because the
intial tables already cannot contain conflicting rows.

Insert duplicate entries in `forwarded_partition_request` table of each
database dump of previous versions, and assert that only a single entry
remains after the migration.

See merge request nexedi/slapos.core!427

See merge request nexedi/slapos.core!426

These scripts were re-implementing the download logic of download_playbook
with the difference being using a different name for the temporary file,
but we don't care about the temporary file name

Another difference was to edit slapcache.cfg once it is downloaded,
this part, we need to keep it.

Avoid bloating the proxy database due to each instance processing
adding the same entries for forwarded requests as duplicate rows
again and again, leading to unbounded growth.

See merge request nexedi/slapos.core!425

   This code is old and unused, so we move into slapos_ecoallocation and drop the installation of the business template.

See merge request nexedi/slapos.core!424

   Use lxml on tests since pyxml was removed (from our build).

   A side effect is the usage of double quote rather them single quote when parse the response, but it is quite minimal change (no impact in production or API, only for this particular test)

    The welcome message can be customizes across projects so we assert the least as possible in relation to the message body.

See merge request nexedi/slapos.core!420

   Unify constraints to check if reference is Unique under SlapOSReferenceConstraint

   Before the introduction of ERP5 Login, it would require to check if reference was unique, by checking also Person documents. This isnt required anymore, since ERP5 Login/Certificate Login and user_id has its own code to check if user is Unique.

   It is essential that reference is Unique, since it is widely used for security and SLA.

   This replaces one alarm present on slapos_administration to detect it, now we may rely on checkConsistency checks.

   This replaces one alarm on slapos_administration for the same purpose

See merge request nexedi/slapos.core!422