No reason to pre-configure test like this

All outdated items should have a validation_state to validated

See merge request !642

This customization is no longer needed and the customized script is now
different in ERP5

  For now, we dont display Consumption details on invoice

   Use getMovementList to get Invoice Cell/Invoice Lines, it allows to get the
    aggregate properly.

   It makes list more consistent.

   Pay Now don't contain the link to pay anymore, so the user
   might use global action to make the payments anyway.

   Return translated 'state' directly and update tests

   Organisation is usually linked as Source Section or Destination
   Section.

   The user don't have access to the Organisations so use Shadow User
   (via script) to get the required information for the printout.

   Bare minimal update to display details, and extend to support Compute Node/Project/Instance Tree Subscriptions.
   Don't display details if the lines don't aggregate subscription requests

   Use directly the Destination Section and display more information if it was one Organisation

Do not try to show results with customer account for now.

Like a Subscription Request, a Subscription Change Request is used to create a new Open Sale Order,
but, it also archive a previous one at the same time.

The purpose is to change some parameters of an Open Sale Order,
and correctly created compensation movement, to ensure the resource
stock is correct.

Stop using discount resource, and reduce the quantity of the consumed software product / service

Only Sale people can create Subscription Change Request.

TODO: check how quantity precision can be defined

The only use case supported for now is changing an Instance Tree's user.

   for Sale Invoice Transaction

   Limit the access from any SHADOW user to specific SHADOW user linked into the context, same as Payment Transaction and Payzen events.

   Roles (Assignee and Auditor) don't change, just become more restrictive to single shadow user.

  Deduplicate script to get shadow user from context, now it relies on base_category_list configured in the role, and output all needed roles (Assignee and Auditor), so the Role configuration can filter it properly.

  This change makes no change on output result for the configured roles.

See merge request nexedi/slapos.core!629

  No need to always set those properties, while no accounting is setup.

  Let the project introduce it if they rely on those payment modes.

   Use subscription_list to calculate Balance amount for the ledger, currency, section from the list. It keeps consistency with the Entity_createDepositPaymentTransaction implementation.

   For now we rely on Base_createExternalPaymentTransactionFromOutstandingAmountAndRedirect for pay subscriptions for customer organisation because it requires update security and review the procedure and how UI will handle it.

  So we invoke directly Entity_createDepositPaymentTransaction with the organisation's subscriptions.

   Use acquisition properly.

   Same as Sale Invoice Transaction to generate payments.

   Merge Deposit and Invoice payments under the same (or nearly similar) implementation.

  Reimplement Entity_addDeposity by creating deposit from a list of subscription

  Ensure will transfer deposit to the proper organisation/person, ledger
  and currency.

  Payment Transaction must preserve website context otherwise it will
  fail over redirections later on.