* add dependencies
* alphabetical order
* restore Compute Node token creation and usage
  Token is now created from a Project
* dependency to slapos_jio
  keep status gadget and the parameter gadget in their original bt5, to simplify rebase
* add missing js dependencies for the json schema validator gadget

* 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
* keep status gadget
* forgot to drop actions

* test: Token creation is allowed to Production users
* add One Time Virtual Master Access Token portal type
  Needed for compatibility with the compute node deploy script
* add slaos_cloud_garbage_collect_one_time_virtual_master_access_token
* trigger alarm once per day

* sale people can view business process
  needed to validate Sale Trade Condition
* allow Production user to create One Time Access Token
* drop slapos_jio dependency

* test: allow to disable alarm when validation a allocation supply
* test: drop reference to an outdated alarm

* fixup rebase

* update xml
* fix InstanceTree_assertSuccessor tests
* fixup slapos_free_compute_partition tests
* more slapos_free_compute_partition tests
* return todestroy status when instance tree is destroyed
* fixup tests for slapos_garbage_collect_destroyed_root_tree
* fixup slapos_update_compute_node_capacity_scope tests
* fixup slapos_stop_collect_instance tests
* fixup slapos_garbage_collect_non_allocated_root_tree tests
* fixup slapos_cloud_invalidate_destroyed_instance tests
* tests: prevent test to impact other tests
* test: commit transaction before end of test
* test: compatibility with _makeComplexComputeNode
* test: fixup remote node creation

* drop accounting_list action
  This action hardcodes rapidspace organisation, and has a different logic from the new implementation
* drop unused scripts
* use the same hosting subscription periodicity per user
  Ensure all invoices for one user will be created at the same date.
  Ensure all users do not use the same periodicity, to NOT generated all system invoices on the same date.
* do not encode url parameter in tales
* allow to check if creating a subscription request is possible
* update subscription history ifvalidation is rejected
* do not generate discount if the price is 0
* set trade_condition_type on temporary Sale Order
* do not set the software release as variation on the Open Order
* update xml format
* assert trade_condition_type are the same
* update Subscription Request view
* configure the Subscription Request like a Support Request.
  Customer as destination_decision
* update constraint as categories were inversed on subscription request
* fixup variable name
* Subscription Request categories were inverted
* invert source_project/destination_project
* source/destination have been inverted
* provice Associate worklist for submitted Subscription Request
* drop Subscription Condition
* drop ecommerce_dependency
* drop Subscription Condition
* drop unused SubscriptionRequest_verifyReservationPaymentTransaction
* drop SubscriptionRequest_verifyPaymentBalanceIsReady
* test: SubscriptionRequest_verifyInstanceIsAllocated was dropped
* display Subscription Request's events
* create an Event when the Subscription Request can not be validated
* drop slapos_update_subscription_request_consistency_state alarm
* drop slapos_subscription_request_process_ alarms
* test slapos_subscription_request_validate_submitted
* use souce_project to find the trade condition
  no need to trick source/destination project anymore, as trade_condition_type is used
* reduce the precision of the discount price
  The idea is to reduce the risk of bad precision when building the related accounting transactions
* drop unused scripts
* drop proxy role
* drop accounting_module/slapos_pre_payment_template
* drop slapos_wechat_pre_payment_template
* drop template_wechat_pre_payment_subscription_sale_invoice_transaction
* drop template_pre_payment_subscription_sale_invoice_transaction
* only try to create subscription request from validated instance/compute node
* reduce frenquency of the subscription request creation alarm
* test: validate items
* only check automated ledger
* reduce conflict on modules
* allow to provide a default price while creating subscription request
* fix getPrice usage
* wait for the request indexaction before launching again the alarm
* put the item reference in the open order title
* set open order title
* improve columns on subscription list
* ensure no price is found if no accounting is expected
* nearly revert ensure no price is found if no accounting is expected
  Do not care of Sale Supply price.
  But keep default_price if provided during the migration
* skip looking for Sale Supply if not needed
* provide more information in the log

* reduce some alarms frequency
  Interaction workflow are needed to speed up everything
* add Base_reindexAndSenseAlarm
* add interactions to speed up allocation
  Use Base_reindexAndSenseAlarm, to ensure object is reindexed, in order to be handled by the alarm
* test: no need to manually call alarms
  Interaction workflow will trigger them
* and fix wrong usage of Base_reindexAndSenseAlarm

slapos_accounting:

* stop using fixConsistency to set hosting subscription periodicity
  Set it directly from the script which create it

slapos_subscription_request:

* do not set the stop_date on the open order
* generate a discount on the first invoice
  If the open order does not start the same day, do not ask user to pay for those missing days
* no need to call OpenSaleOrder_updatePeriod when creating the open order

* test: create deposit payment to validate the subscription
* test: update related document count

* test: define currency on the organisation
* test: scenario for money deposit
* test: typo
* test: apply tax amount only if the resource is taxable
* allow shadow user to view Organisation
* test: reduce number of alarm calls

* cleanup request when instance is not subscribed yet
* stop instance tree propagation on instance_slap_interface_workflow
  Some alarm call request directly on the Instance Tree (this is expected)
* rename Service_getSubscriptionStatus to Item_getSubscriptionStatus

* test that Subscription Request is created from Compute Node
* drop SubscriptionRequest_processStopped
* drop SubscriptionRequest_processStarted
* drop SubscriptionRequest_processOrdered
* drop SubscriptionRequest_processConfirmed
* drop SubscriptionRequest_processRequest
* drop SubscriptionCondition_renderKVMClusterParameter
* drop Base_instanceXmlToDict
* drop SubscriptionCondition_renderParameter
* drop testSlapOSERP5VirtualMasterSubscriptionRequestScenario
* ensure Subscription Request is consistent
* allow to choose the currency when creating a Subscription Request
* try to close the Subscription Request as soon as user paid an invoice
* block subscription process if there is no deposit
* do not accept new services if the virtual master subscription state is not expected
* use Base_reindexAndSenseAlarm

* update one more test
* test_virtual_master_slave_on_same_tree_without_accounting_scenario
* test_virtual_master_on_remote_tree_without_accounting_scenario
* test_virtual_master_slave_instance_on_remote_tree_without_accounting_scenario
* test: really disable accounting

* test: use Person_addVirtualMaster to create project
* test: login as user to request the instance

* init preferences in test
* test: wip accounting scenario
* test:  slapos_subscription_request is installed again

* test: new parameter
* test: keep compatibility with previous addProject