The new versions do not include any price informations.
It is needed to create new Trade Condition which inherite from those versions.

Update preference to use those latest trade conditions.

slapos_accounting: factorise code

slapos_wechat: use reference sale trade condition

slapos_erp5: check sale trade condition reference

sale trade condition are versionned.

Clarify trade condition title

Prices are defined on Supply Line inside Sale Trade Condition.

Drop prices from Subscription Condition.
Instead, link the Subscription Condition to a Sale Trade Condition.

Apply the Sale Trade Condition on the created Open Sale Order.

Stop duplicating properties from the Subscription Condition to the created Subscription Request.

Payment is managed by the 'payment' category, and not the language.

This allows to remove all '==zh' conditions.
Instead, use custom Sale Trade Condition.

slapos_accounting:

* generate one open order per instance tree
* create empty contraint property sheet for open order
* only one line per open order
* workaround wrong select returning a result multiple times
* XXX break instance tree periodicity. Must move to hosting subscription
* rename script for hosting subscription
* revert failure error
* force open order line to have an Instance tree and a hosting subscription
* hosting subscript will host the date info
* set open order periodicity on the hosting subscription
* typo
* hosting subscription will contain the periodicity
* create hosting subscription
* fixup start/stop date confusion
* add hosting subscription workflow
* stop using Instance Tree as Subscription Item
* move periodicity view on hosting subscription
* simulation is expanded from Hosting Subscription
* validate hosting subscription
* check all aggregate value
* revert aggregate tester
* simulate from hosting subscription
* constraint is on hosting subscription
* interaction are on hosting subscription
* open order line has 2 aggregate
* do not create open order if it was not allocated
* script renamed

slapos_erp5:

* open order line have 2 items now

slapos_cloud:

* open order line has 2 items now
* hosting subscription have a workflow again
* add hosting subscription template
* update HS_view

slapos_subscription_request:

* periodicity is on hosting subscription

* force open order to be created to allocate
* only check validated open order
* check open order consistency before allocating
* call script on the real web section

* drop not needed condition
* factorize some code

* drop template_software_installation
* drop template_instance_tree
* drop template_member

* WIP migration scripts
* migrate compute node
* do not skip some migration
* migrate more properties on compute node
* migrate software installation
* migrate compute already linked to a project
* trigger instance tree migration
* migrate more instance trees
* migrate Instance Tree, Software/Slave Instance
* migrate instance tree
* do not create not needed activities
* migrate instance tree linked to an existing project
* migrate existing subscription requests/projects
* allow to run the migration multiple time
* move an instance to the same virtual master than his main compute node
* if all instances are linked to the same project, move the computer to that project
* migrate computer network
* move to personal if no instance allocated
* partially destroyed instanc ewill move to personal
  Unallocated instance will use remote note
* force migration to remaining compute nodes
* break network link if not consistent
* create Remote Node and Remote Instances
* reduce concurrency on instance tree creation
* try to reduce conflict
* some sla xml seems broken
* instances do not always have a predecessor
* it seems activity is also triggered on already migrated instance
* some instances were manually invalidated...
* do not go too slowly
* generate a graph showing the virtual master relation
* another report
* prepare migrating Instance Tree to a remote node
* change report output
* fixup instance virtual master migration
  do not forget to also move the successor to the new virtual master
* do not fail if already migrated
* create Software Product (and its variations)
* create Instance Node
* create allocation supplies
* control trade condition reference length
* migrate existing open order
* migrate assignments
* slow down execution of the next steps
* ensure project exists
* fix getTotalPrice usage
* slave instance slap_state is not indexed
* run instance tree migration multiple times
* report broken instances
* fixup payable Subscription Request creation
* migrate Support Request and Event
* improve error message
* keep the payable instances on the payable projects
* payable instance are now kept on payable virtual master
* do not crash if instance was already migrated
* report missing prices
* show product
* create assignment only if user has validated instance tree

* test panel scenario
* validate testFunctionalSlapOSPanelStyle
* dependency
*  HARDCODED data/user bootstrap
*  passwd policy
* use theia directly in the test
* WIP shared instance test
* shared instance test
* limit Software Instance to manager only
* add basic payable service test
* randomize logins
* check consistency at the end of the test
* slapos_panel_ui_test: check all project related documents as project manager
* execute all alarms at the end of the test to detect unexpected side effects
* ensure we can activate slave allocation on same tree
* test remote node allocation
* test Slave Instance allocation on Remote Node
* ensure request limit the list of release/type based on allocation supply
* test Upgrade Decision actions
* test Computer Network creation
* use Person_addVirtualMaster
* do not explicitely call alarms
  rely on interaction workflow instead
* add Software Product to create Subscription Request
* add Sale Supply for virtual master
* fixup to generate subscription request and use the instance parameter editor
* fixup Instance editor usage
* set reference on the Trade Condition
* fix consistency of other documents before running the tests
* request instance action has been modified
* fixup accounting scenario
* text: configure trade_condition_type on the Sale Trade Condition
* test: assignments are automatically created when adding a virtual master
* fix Trade Condition creation
* update selector used by the new jsoneditor
* discussion_thread_reader gadget is now used
* do not check Web Site consistency
* no need to define the currency manually
* search link has been removed. Access global search manually
* WIP fixup after frontpage changed
* WIP fixup after frontpage changed
* do not check System Preference

* add SlapOSVirtualMasterSourceProjectConstraint on Upgrade Decision
* software product must be linked to a project
* create Software Type portal type
  It is a variation of a Software Product
* rename Software Type to Software Product Type Variation
* add Software Product Release Variation portal type
* force default use/base_contribution on Software Product
  Didn't find another way to do it (init script requires data migration)
* require Software Product to have at least one Type and one Release
* store url_string on Release Variation
* use edit_workflow on Variation portal types
* use the jump action to access Software Release
* add dedicated form to view Release
* add Software Type view
* set SoftwareProduct default quantity unit
* support document without categories property
* add constraint to ensure quantity unit of a Software Product is defined
* drop Software Release configuration. Drop hardcoded template only used in tests
* fixup
  See 1173ea0e
* drop Compute Node upgrade
  This is now handled manually by updating the Allocation Supply
* stop allowing Upgrade Decision Line creation
* Upgrade Decision is a ticket
* wip upgrade decision redesign with allocation supply
* not commited script
* really compare url strings
* update upgrade decision view
* only create upgrade decision for SOftware Instance for now
* set the compute node on the test allocation supply
* drop not used scripts
* remote tests from dropped scripts
* mark test to check
* test alarm_instance_tree_create_upgrade_decision
* drop upgrade_scope
* test upgrade decision creation for not allocated instance tree
* test Upgrade for allocated Software Instance
* drop deprecated tests
* root shared instance can not be upgraded by Allocation Supply on the same tree
* upgrade not allocated or allocated on remote slave instances
* update not allocated in there is instance node supply
* test upgrade Instance Node
* drop unused InstanceTree_getUpgradeSubscriptionRelatedValue
* drop UpgradeDecisionLine_cancel
* drop Upgrade Decision Line view
* drop SoftwareProduct_getSortedSoftwareReleaseList
* fix upgrade decision list view
* drop InstanceTree_isUpgradePossible
  No way to know which software release url on instance will request.
* drop UpgradeDecision_processUpgrade
* drop Base_acceptUpgradeDecision
* drop Base_rejectUpgradeDecision
* drop reviewRegistration
* check created upgrade decision
* do not propose again to upgrade if decision has been rejected
* no need to check all rejected decisions
* do not put newly create decision in started
  Ask review from manager
* drop UpgradeDecision_notify
* drop UpgradeDecision_notifyDelivered
* drop reviewUpgrade
* drop UpgradeDecision_getAggregateValue
* drop approveRegistration
* drop upgrade_slap_interface_workflow
* drop UpgradeDecision_requestChangeState
* drop slapos_pdm_auto_cancel_upgrade_decision
* use UpgradeDecision_processUpgrade
* alarm to destroy software installation
* drop unused template
* configure Upgrade Decision worklist
* drop not needed script arguments
* add Upgrade Decision constraints
* method moved to global mixin
* do not upgrade if there is no instance yet
* create upgrade decision as soon as Allocation Supply is validated
* workaround to prevent breaking the instance when classes are live reloaded
* test: disable alarm when creating an allocation supply
* test: disable alarm
* software_release is an optional variation
  We can not update the Open Order every time one Instance is upgraded
* sort SoftwareProduct getVariationBaseCategoryList's result
* update xml format
* optional_variation_base_category_list are not set in variation_base_category_list
* force software change from Upgrade Decision
* drop template_instance_tree
* allow to force upgrade to a specific release
* rely on self instead of one a global
* drop view_related_upgrade_decision on Compute Node
  Deprecated for a long time

* project reference is required for compute node
* require a project when requesting an instance tree
* Remote Node has no user_id
* _makeComplexComputeNode need a project
* product/release
* Release
* test
* no source administration on compute node
* project on compute node
* fix person assignment
* proj reference
* test
* project reference
* getSoftwareReleaseListFromSoftwareProduct is related to a project
* getSoftwareReleaseListFromSoftwareProduct requires a project reference
* release are not published anymore
* test: bypass subscription request
* drop template_compute_node

* source_administration is not used anymore on Compute Node
* add virtual master contraint to tickets and events portal types
* propagate project from Regularisation Request to event
* delivery/movement must use source_project instead of follow_up
* set source_project on event
* stop setting person as source_project
* copy project from ticket to the new event
* utf-8 encoding issue
* XXX disable regularisation request alarm
* Regularisation Request Module acquires local roles
  See other modules
* drop upgrade_scope
  Upgrade is managed by Allocation Supply.
* drip upgrade_scope usage
* drop Upgrade Decision Line usage
* lint test
* fix slapos_crm_check_software_installation_state alarm test
* fixup slapos_crm_check_compute_node_state tests
* fixup slapos_crm_check_instance_in_error test
* fixup slapos_crm_update_support_request_state tests
* fixup slapos_crm_send_pending_ticket_reminder test
* fixup slapos_crm_trigger_stop_reminder_escalation tests
* fixup slapos_crm_trigger_stop_acknowledgment_escalation test
* fixup slapos_crm_trigger_delete_reminder_escalation test
* fix slapos_crm_trigger_acknowledgment_escalation test
* fix slapos_crm_stop_instance_tree test
* fix slapos_crm_invalidate_suspended_regularisation_request test
* fix slapos_crm_delete_instance_tree test
* fix slapos_crm_create_regularisation_request test
* drop slapos_crm_check_update_allocation_scope tests
* do not require source_project on crm
* fixup rebase: drop Instance Tree Module | slapos_resilience_usage_report
* drop preferred_support_request_template_property
* drop slapos_crm_support_request_template
* fixup slapos_crm_create_regularisation_request tests
* reactivate slapos_crm_create_regularisation_request
* test slapos_crm_invalidate_suspended_regularisation_request is ok
* test slapos_crm_check_software_installation_state
* test slapos_crm_check_instance_in_error
* test slapos_crm_update_support_request_state
* desactivate Person_getSubscriptionRequestFirstUnpaidInvoiceList
* drop Person_getSubscriptionRequestFirstUnpaidInvoiceList
* do not count all Support Requests
  limit parameter with count is meaningless, as count return 1 result
* update Base_getSupportRequestInProgress usage
* XXX disable ticket.notify and ticket.requestEvent
* wip script to create Support Request and Event
* search a matching Trade Condition to generate a Support Request
* update ComputeNode_checkState to use new scripts
* test ComputeNode_checkSoftwareInstallationState
* deliver outgoing events
* test InstanceTree_checkSoftwareInstanceState
* Project_createSupportRequestWithCausality already checks if Support Request exists
* no need to check twice the object portal type
* test SupportRequest_updateMonitoringState
* activate one more alarm
* revert  Send Mail on pending tickets
  nexedi/slapos.core!417
  Virtual Master's manager are responsible to handle the tickets through their worklist.
  Not user.
  Virtual Master's manager can send email from the Ticket to directly ping a user.
* drop ticket_slap_interface_workflow
* test ComputeNode_hasContactedRecently
  Do not check if there is a packing list. It is unrelated to the contact.
* Base_getOpenRelatedTicketList was dropped
* ComputeNode_checkAndUpdateAllocationScope was dropped
* test: simplify
* set comment in the event workflow history
* send Mail Message
* unify event creation
  Reuse Ticket_createProjectEvent
* do not pass a empty list of node_uid
* no need to manually handle the notification message
* create the Regularisation Request from a Trade Condition instead of a template
* use notification message title instead of the ticket title
* use Entity_hasOutstandingAmount
  Entity_getOutstandingAmount is meaningless in case of multiple source_section and multiple currencies.
  Entity_hasOutstandingAmount will only report True or False.
* test RegularisationRequest_invalidateIfPersonBalanceIsOk
* test RegularisationRequest_checkToTriggerNextEscalationStep
* test RegularisationRequest_triggerStopReminderEscalation
* test RegularisationRequest_triggerStopAcknowledgmentEscalation
* test RegularisationRequest_triggerDeleteReminderEscalation
* test RegularisationRequest_stopInstanceTreeList
* test RegularisationRequest_deleteInstanceTreeList
* fixup RegularisationRequest_checkToSendUniqEvent tests
* fixup RegularisationRequest_checkToTriggerNextEscalationStep tests
* fixup InstanceTree_stopFromRegularisationRequest tests
* fixup InstanceTree_deleteFromRegularisationRequest tests
* drop slapos_crm_regularisation_request_template
* drop slapos_crm_web_message_template
* drop preferred_web_message_template_property
* drop slapos_ticket_trade_condition
* drop update_destination_for_slapos
* drop allocation_tester
* drop template_software_installation
* drop template_instance_tree
* drop template_member
* test: fixup person title
* test: fixup: ensure tickets can be created
* test: fixup creation of instance tree
* test: fixup instance tree creation
* test: ComputeNode_getTicketRelatedList was dropped
* test: rss feed will be used by virtual manager production
* test: ticket.approveRegistration was dropped
* ExactMatch
* drop preferred_cloud_contract_enabled_property
* only submit the newlu created Support Request
  end user can not validate their submitted ticket
* drop jump_related_slapos_item
* drop outdated SlapOSSupportRequestConstraint
* submit created event
  This allow to separate new ticket from the one currently handled
* constraint was dropped
* test: create test ticket in submitted state
* support request are created in submitted state

* add new business application categories
* export edger category
* automated ledger is not only for accounting
* drop allocation_scope/open categories
  All compute nodes are public now
* add use/trade/deposit category
* do not use the same title for 2 categories
* Add trade condition type categories.
  This will be used to automatically select a Trade Condition in slapos_accounting

* drop default_or_child_aggregate_reference
* drop  default_or_child_aggregate_uid catalog key
* drop unused follow_up_default_or_child_aggregate_uid
* drop causality_subscription_request_related_uid related key

This make usage of the relationfield nicer.

See merge request nexedi/slapos.core!596

See merge request nexedi/slapos.core!595

When an user belonged to a group before running slapformat, the user was previously
removed from that group. This commit avoids it by simply appending SlapOS
additional groups.

  This API will be refactored on the new API

See merge request nexedi/slapos.core!591

   In the case of checkNotCycle, the re-recheck would always fail on a disconnected tree first, so it is mandatory patch the checkConnected (to skip) during the tests.

See merge request nexedi/slapos.core!579

- change url parameters for dispatch link
- use monitoring app landing url
- add url-user-pass parameters to monitor url