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 nexedi/slapos.core!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)

   The input_movement_list weren't properly filtering causing grouping references been set with it's late occurency.

   It makes requests as non-subscription and for subscription cases, and assert if the invoice is correctly linked via simulation

See merge request nexedi/slapos.core!277

  This is probably required multiple renames or upgrade project code base

  This fixes name convention tests:

     /portal_skins/slapos_crm_monitoring/SupportRequestModule_viewExportMonitorOPMLList
     'message': 'erp5-Guideline.Form.Report.Dialog.Is.Postfixed.With.Dialog: Dialog form name must follow ${portal_type}_view.*Dialog naming'

     /portal_skins/slapos_crm_monitoring/SupportRequestModule_viewInstanceMessageList
     'message': 'erp5-Guideline.Form.Report.Dialog.Is.Postfixed.With.Dialog: Dialog form name must follow ${portal_type}_view.*Dialog naming'

     portal_skins/slapos_crm_monitoring/SupportRequestModule_viewSupportRequestMonitorLinkList
       'message': 'erp5-Guideline.Report.Name.Uses.Portal.Type.Followed.By.View.Report.Name.And.Report: Report form name must follow ${portal_type}_view.*Report naming'