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'

Because some programs did not have proper configuration for log files, they
were using automatically generated file names for log files. Correctly
define stdout_logfile configuration for all programs, used with
redirect_stderr=true, so that both stderr and stdout are in the same log
file.

  This is a safe measure in case the alarm to delete the instance is temporarily disabled.

    This is a initiall prototype (as experiment) to be moved and improved elsewhere later.

See merge request nexedi/slapos.core!276

* Calling these constraints on Subscription Request brakes as some property are missing in subscription requests.

* transaction_id is the combination of the transaction_date and the transaction number of the day

In 51f89902 (slapos/cli/entry.py, slapos/cli/format.py, slapos/format.py:
Do not double the log output when "slapos node boot" failed., 2017-05-11)
we fixed a problem that every failure during boot causing twice more output
(which filled up the disk very fast), but a side effect was that using
--log-file no longer cause messages to also go to the console.

The "Always send higher-level messages to the console via stderr" comment
in entry.py seems that this was always intentional to output messages on
the console.

Keep the same "don't configure again logging system when it's already
configured", but implemented in a slightly different way, because since
a FileHandler is a StreamHandler, the check of already having a
StreamHandler was true also for the case where --log-file added a
FileHander (a few lines above, also in configure_logging method)