Payzen has a delay between the Charge and the transference to the bank. This requires the accountant to generate yet a new accounting document to represent it.

     This might replace "Bank" for automation, since "Bank" requires that the money been accurately in relation to Bank Sheets.

    If set, causality is a Subscription Request, and it should be always splited.

   Use shadow user to access Account document, this prevent us to setup complex security.

   The asserts and verification should be done as manager to present set unecessary security roles.

    Those documents are expected to be published when they are accessible

   This isn't compatible with the actuall usage, if we want to keep this, we should install networkcache_erp5 business template (and use groups/security from there).

When slapproxy forwards a request to an external master it is seen as
coming from the slapproxy and the original requester's id is lost.

This means forwarded requests from different requesters can collide.

e.g. two partitions request a frontend and when the second request is
handled the external master updates the first frontend to redirect to
the second partition instead of creating a second frontend.

To avoid collisions, the id of the requester as seen in the slapproxy
is prefixed to the instance name (partition reference) in the request:

- case 1: requester is embedded partition => prefix with partition id
    e.g. 'myinstance' -> 'slappart0_myinstance'

- case 2: requester is user => prefix with 'user'
    e.g. 'myinstance' -> 'user_myinstance'

See merge request nexedi/slapos.core!282

There is no reason to name regions so explicitly (like France or US), just
use generic and understandable region name (like Europe or North America).

Chinese endpoints are named via their operating telecoms, as this is like
region (latency, speed).

  Since wechat is used on those tests.

   Those properties is whenever we want to use different defaults for chinese and non-chinese organisations. Usually, due wechat/payzen payments.

   When you have different companies per Subscription Conditions

logging is configured globally in SlapOSApp.configure_logging and:
 - if logging to file is enabled, it is logged with maximum level
 - logging on the console depends on --quiet / --verbose command line flags

Default log level of this logger was DEBUG, which is just fine: the logger
emit all messages and the file/console handler decide to output them or not

Because we configure logger after Flask initialize its own logging, for
Flask >= 1.1.2, we remove Flask logger as described in
 https://flask.palletsprojects.com/en/1.1.x/logging/#removing-the-default-handler
Since this is internal API which doest not exist on old version of Flask, we
adjust requirements to require a recent version of Flask.

See merge request !280

   Subscription request workflow uses simulation_state rather them validation one.

   What happens when user don't pay reservation.

     Since we use Caddy rather them apache by default, change the field to input a value on tests.

slapos_subscription_request: As dates are simetrical on Invoice and Payment, the value is not negative anymore

   This with price not zero is covered by another tests.

   Failures:

      portal_skins/slapos_subscription_request/SubscriptionRequest_checkRelatedAccounting:5:2:Dangerous default value {} as argument (dangerous-default-value)
      portal_skins/slapos_subscription_request/SubscriptionRequest_checkRelatedAccounting:15:2:Unused variable 'refund_service' (unused-variable)