This customizable type based method is used in "Attach Document" and
"Scan Document" dialogs, to set a default value in the dialog for the
publication state field.

Extend "Attach Document" to have the same feature as in "Scan Document"
so that user can directly choose the state when uploading a document.

This simplifies a bit document_scanner, which can reuse the code that is
now in Base_contribute

document_scanner: introduce a customizable type based script to suggest a title for scanned document

Unlike when we attach a document, where the title comes from the filename of the attached document,
when we scan document we don't have any filename. There's a default behaviour of using the current date, so that title is not empty, but in some cases we can define a script to suggest a better title, for exemple when scanning an invoice, we can suggest using supplier name and the invoice title.

ingestion's dialog uses some type based methods for customizability, use
same type based methods here.

The default group of documents attached to accounting transactions can be
taken from the group of sections

Base_viewNewFileDialog/your_publication_section allows to easily suggest
a default publication section to the user, but the "group" was not so
easily customizable, it was just getting from document or user.

Introduce the same mechanism as for publication section, a type based
script that can be defined for each portal type.

On documents, we have an "Export" action for OOoDocument_viewConvertDialog.
When erp5_ods_style is installed, "Export to Spreadsheet" is added as a global
action. Both these actions were translated as "Exporter" in french, which is
confusing and a bit incorrect.
Use a proper, different translation for "Export to Spreadsheet"

This test was comparing lines returned in unspecified order, sort the lines
to be sure.

fix pylint warnings

See merge request nexedi/erp5!1363

"contact us" feature of erp5_web uses erp5_crm

testTemplateTool depend on the actual order of installation of business
template, so update it now that the order has changed.

configurator scripts also had to be updated, so that
erp5_ingestion_mysql_innodb_catalog is installed before erp5_web/erp5_crm
because since erp5_crm depends on ingestion, it will install
erp5_ingestion_mysql_innodb_catalog, which has new tables and SQL methods
for indexation, so it needs to be installed with `update_catalog=True`.

As we can see here, configurator uses installBusinessTemplateListFromRepository
to install business templates one by one (in the same order that they are
added with addConfigurationItem), and pass update_catalog only for
business templates which add new tables/indexation methods and needs a
catalog update after install, but what happened is that we install
erp5_web with update_catalog=False, which will install
erp5_ingestion_mysql_innodb_catalog, also with update_catalog=False so
the activities to install business templates fail with errors like:

    ProgrammingError: (1146, "Table 'erp5_test_*.email' doesn't exist")

Since 459093f3 (ERP5Form: implement a basic checkConsistency for
ProxyField, 2021-01-26) we can detect inconsistentencies in ProxyFields
internal data structures. These are the changes after using
checkConsistency(fixit=True) for erp5_web

This relation field is used to select the web pages that will be displayed,
by using the standard ERP5 document management feature of selecting the
best applicable page with the same reference, but this list did not show
the reference of the web page

for security reasons, info on users, or existence of usernames shouldn't be leaked from the system.

manage_FTPget is an API to serve the file content to response, it is not
suitable to just get the file/page template content like we need here.
It was causing issues when running through activities, because timerserver
responses does not have the setBase method, but is also wrong because
large files are streamed to response directly.

Zope does not really offer an unified API to get the source of page
templates or files, except the PrincipiaSearchSource method which it uses
for its builtin search engine. It seems suitable to use here as well.

Also add a test for the case where web pages are in a OFS.File, only
the case of PageTemplate was covered.

Use the `ui-list-grid` class on a `ul` element.

```
return gadget.getTranslationDict([Foo])
  .push(function (translation_dict) {
    console.log(translation_dict['Foo'])
  });
```

```
return gadget.getCommandUrlForDict({
  foo_key: {
    command: 'display'
  }
})
  .push(function (url_dict) {
    console.log(url_dict.foo_key);
  });
```

erp5_web_renderjs_ui_test: Add page to be used as example of links to extra menu and cover it with test

The query planner does not seem to notice that we are trying to know if
any row exists matching a set of dependency values, and it keeps scanning
multiple row for each value - which is unproductive.
So split dependency queries from (pseudo-code)
  WHERE <column{,s}> IN <values{, pairs}>
to unions of
  WHERE <column{,s}> = <value{, pair}> LIMIT 1
which produces query plans which do stop immediately when finding a
candidate row.
On a serialization_tag query with 40 values and real-world indexations,
this reduces the number of rows scanned by mariadb from 500 (<10%
efficiency) to 40 (100% efficiency).
The produced SQL is significantly larger (~3x, around 500kB on
real-world sample data, but may vary a lot depending on value length),
but if this has any effect is is more than compensated by the improved
query plan efficiency.

See merge request nexedi/erp5!1355

For test components, we don't use getBusinessTemplateList but define the
business templates to be installed as (test) dependencies of the business
template containing the test.

update test after c3eb0b30 , because non editable editor now render HTML

See merge request !957

See merge request nexedi/erp5!1353

currently with a test that tests document_connection

Ensure float/integer field can align right on the listbox
See cfbc621b

This was removed from products in previous commits

Nowadays instead of creating many portal types, we use `use` category to
separate different types of movements, so it makes sense to filter by use,
the same way that we already were able to filter by portal type.

Let's be consistent and use the default size.