* drop support request template preference
* drop my_preferred_support_request_template
* stop using getPreferredSupportRequestTemplate
* drop Subscription Condition usage
* break Base_getSupportRequestInProgress
  Use causality category instead of aggregate, to link the Ticket to the context document (instance, node, ...).
  Aggregate must be used to define the item of the movement resource.
  Break the parameters and use the context to define the causality value.
* use causality to link the  Ticket to the context document
* XXX disable person.notify & person.requestSupport
  I don't get why there are 2 transitions for now.
* drop ComputerNetwork_viewComputeNodeList
* drop notify and requestSupport transitions
  They have been replaced by python script and alarms
* test: person.notify has been dropped
* drop slapos_crm_regularisation_request_template
* Do not allow user to change the release/type/shared status
* no need to use a tag if context is not reindexed
* allow to force software change
* speed up Base_reindexAndSenseAlarm execution
* drop my_preferred_default_pre_payment_template
* drop default_pre_payment_subscription_invoice_template
* drop getPreferredAggregatedSubscriptionSaleTradeCondition
* test: drop unused functions
* drop preferred_aggregated_sale_trade_condition
* drop preferred_aggregated_sale_trade_condition
* test: drop reference to slapos_aggregated_trade_condition_v3
* test: drop test from dropped interaction
* test: role is not required on a Person
* test: do not invalidate instance to not unlink
* test: create Trade Condition when Project is accountable
* drop slapos_crm_web_message_template
* drop my_preferred_web_message_template
* drop template_pre_payment_subscription_sale_invoice_transaction
* drop preferred_default_pre_payment_subscription_invoice_template
* drop slapos_accounting_instance_delivery_line_template
* drop slapos_aggregated_consumption_trade_condition
* drop preferred_aggregated_consumption_sale_trade_condition
* drop unused template
* drop template_computer_model
* drop template_hosting_subscription
* drop template_software_installation
* drop template_compute_node
* drop template_instance_tree
* drop template_software_instance
* drop template_member
* drop drop template_software_instance
* drop template_software_instance
* drop template_software_instance
* add afterClone scripts
* test: check remote node parameters propagation
* try to create an upgrade decision for a remote instance
* test: add checkRemoteInstanceUnallocation method
* XXX stop invalidating Slave Instance
  TODO: Instance on Remote Node must propagate their destruction, before being invalidated
* instance must be invalidated before unallocating it
* drop not needed script
* invalidate Slave Instance allocation on a Compute Node
* trigger invalidation as soon as an Instance is destroyed
* alarm must visit allocated Slave Instance to invalidate them
* report software url of the linked instance, even if it is in destroyed_state / invalidated
* test: slave are not directly invalidated as soon as it is destroyed
* propagate remote node destruction
* do not crash if no instance is found
* ExactMatch
* drop comments
* keep compatibility with project_guid sla
* allow to propagate a single instance
* add subordination category on Remote Node
* try to wait for previous alarms to finish before triggering a new one
* priority 3
* do not call activeSense concurrently
* prevent activeSense to be called concurrently
* reduce number of activities
* do not loop
* drop preferred_cloud_contract_enabled
* stop using hateoas web site
* change the skin selection to register
* test: create needed bank account

otherwise, new categories are not installed

* test: assignments are automatically created when adding a virtual master

* test: fixup trade condition specialise
* configure 2 modules's business_application
* do not allow user to see each others
  Do not allow personal information to be visible to anybody
* allow Sale agent/manager to handle Assignments
* test: assignments are automaticall created when creating a virtual master
* test: fixup
* drop organisation pages

* assert trade_condition_type are the same
* update Subscription Request view

* test: slapos_panel_compatibility was added
* test: create Trade Condition for Deposit
* test:  slapos_panel_compatibility skin selection

We can not update the Open Order every time one Instance is upgraded

* search Sale Trade Condition by trade_condition_type
* set trade_condition_type on temporary Sale Order

* readd translation bt5 dependencies
* configure trade_condition_type on the Sale Trade Condition

This will be used to automatically select a Trade Condition in slapos_accounting

* dependencies

* status gadget portal _type is provided by the python script
* do not mess with cursor used by browser
  it only confuses users
* do not display links without href
* disable gadget status onLoop
  Instead of jio.get, the paramers must provide the url to query,
  otherwise, it is not possible to use this gadget in the full ERP5JS
* reintroduce all stuff from slapos_jio_before_deletion
  my branch is not ready to drop everything

* project does not have status gadget anymore
* use getPreferredHateoasUrl to generate the compute token
  improve consistency with slaptool (configure this value in 1 place only)

onLoop must be fixed probably

* add slaos_cloud_garbage_collect_one_time_virtual_master_access_token

* only run alarm once per day
  Interaction workflow are now supposed to trigger the alarm when needed
* run alarm once per day

keep status gadget and the parameter gadget in their original bt5, to simplify rebase

* keep status gadget
* forgot to drop actions

* drop Compute Node Token previous implementation
* erp5_web_renderjs_ui | RJS is managed by erp5_web_renderjs_ui bt5
* move most stuff to slapos_jio_before_deletion
  Keep slapos_jio minimal to simplify the rebase on the files to keep

Needed for compatibility with the compute node deploy script

* add dependencies
* alphabetical order
* restore Compute Node token creation and usage
  Token is now created from a Project