* Rename WorkflowConfigurator PropertySheet to ConfiguratorWorkflow.
* Add ConfiguratorWorkflowTransition PropertySheet for transition_form_id.
  => Should it be moved to standard 'action' instead?
* Avoid defining Configurator-specific API in Workflow API, such as
  initializeDocument(). TODO: What about:
  - state.getAvailableTransitionList()
  - state.executeTransition()
  - state.getWorkflowHistory()
  - state.undoTransition()
  => erp5_configurator_standard:testStandardConfigurationWorkflow

* Add WORKFLOW.{scripts,transitions...} property which is just a ComputedAttribute
  returning a dict (TODO: Instead of a dict, this should be ContainerTab to have
  objectIds()...).

* Allow a Workflow Script to call another one by overriding portal_workflow.__getattr__.
  With DCWorkflow, `container` was bound to its parent (WORKFLOW.scripts which is a
  mapping), but now `container` is bound to the WORKFLOW itself as Transitions, Scripts
  and Variables are all at the same level. This is not very efficient but this is only
  in DCWorkflow compatibility mode after all.

  The initial implementation was creating a `ScriptContext`, a temporary object with
  all scripts of the current Workflow added. However, this required changing existing
  Workflow Script code and especially this did not work with the following use case:
  1. Script Context is created before calling a Workflow Script.
  2. That script calls a Workflow Script from another Workflow.
     => This will fail as ScriptContext is only created for the Workflow.

This commit is going to be squashed before merging to master.

Ignore for now the differences between ERP5Workflow implemented for Configurator
a long time ago and "new" ERP5 Workflows.

This commit is going to be squashed before merging to master.

Work done by Wenjie Zheng, Isabelle Vallet, Sebastien Robin and myself.

* Soap Duplicate and Soap Cancel functions have been discontinued due to lack of usage
* OrderId is now necessary in order to retrieve Transactions

My suggestion of using sorted in
nexedi/erp5!1373 (comment 129103) was wrong,
ERP5 document do not sort in deterministic order. Use a key function to make
sure we get results in same order

See merge request nexedi/erp5!1373

For two reasons:
- In previous version, query would lose Embedded Documents, lacking a left join in follow_up_uid
- In large instances the previous version was many times slower

Also,
erp5_dms: Add a test for Base_getRelatedDocumentList

To check it works correctly with both related (follow_up)
Documents and with sub-object Embedded Files

in 772d8fed (configurator_standard: use specific sale and purchase
business processes, 2020-07-16) we introduced scripts to look up
dynamically accounts to use for expense/income and VAT accounts, from
supply lines, but this accidentally broke the case where no account can be
found on supply lines: in this case, the accounting line was not generated.

Ideally, there should be fallback accounts, to keep the same behavior and
also to prevent generation of incomplete transactions.

Review the scripts, so that the "Dynamic" scripts fallback on the account
defined on the trade model path if not found and introduce new scripts,
where the account is not taken dynamically, but only from the trade model
path, for use on the payable/receivable lines (where we don't want to
lookup the account dynamically, otherwise we'll use same account as for
expense/income)

This omit_grouping_reference key was not set as selection parameters, so
Node_getAccountingTransactionList could not find it in selection when running
in deferred mode.

In non deferred mode, it was working, because selection is set with values from
request and it was same request, but deferred style uses activities, so it's
different requests.

When IBAN is defined, use it by default for reference. IBAN is used by
default all over europe, so when it's set it should be used by default for
reference.
Mixing IBAN and other properties does not make sense, so this change
should not have unexpected side effects.

We also update "edit_order" on BankAccount_view so that title properly
fallbacks on reference when reference is iban.

To ease "manual" (ie. not from payment rule simulation) creation of payments,
update "create relate payment" so that it suggests the payment mode and the
payment date from payment conditions of the invoice's trade condition.

See merge request nexedi/erp5!1369

Use editor gadget to render the output as raw data.

Use the page class to improve xhtml style rendering

* enable more elements/attributes
* show table cell's border
* reduce table width
* support align="center"
* only use sans-serif font like ckeditor

erp5_ui_test: textarea use an external validator as required prevent submitting

Avoid propagate empty value to change_state and only set new value if it is in modification_dict

This introduce a new utility script Invoice_getPaymentDueDate and removes
the previous attempts, SaleInvoiceTransaction_getDueDate and
TradeCondition_getDueDate that were never used.

See merge request nexedi/erp5!1367

- Column Version length is extended from 10 to 255 so it can store md5sum's lenght (32 characters) that is needed by data streams created during ebulk tool ingestions used in wendelin.
- New column Size is needed to speed up ebulk tool and can generally be useful for DMS, so that we can search/sort document by size.

File is a top-level module document, like PDF, Text Document etc, so it
should have its own security definition and should not acquire local roles.

For cases where files are embedded as sub documents, we are using Embedded
File, which acquire local roles.

In "Attach document" action of erp5_ingestion, the default publication section of attach document suggested in the dialog is defined by a type based script.

We could do the same for group, so that we have a script that is easier to customize for specific cases. One use case is for accounting transactions, the group is usually the group of the entity where the document is attached.

Also, we could enable type based script in document scanner dialog, which is very similar to attach document dialog, but it was not using the scripts.

Similarly, we introduce a script to suggest a title in document scanner.

Another difference between "Attach Document" and "Scan Document" is that the later had a "publication state" field, allowing user to choose a state for the created document. We extend this to "Attach Document" as well and introduce another customizable type based method to be able to configure a default value.

See merge request nexedi/erp5!1359

They are often used to achieve surprising styling