* Add bt5 dependencies:
  + erp5_demo_maxma_rule: Invoice*Rule rules.
* Move Documents used by several bt5 to erp5_core rather than add depends on erp5_core.
  Once migration of Products to ZODB Components will be finished, there will be moved to
  their appropriate bt5s as it would be complicated to reorganize bt5s too at this point.
  + Invoice{Line,Cell}: used by erp5_payroll.

Clicking on a button tag with an embedded img tag crashes everything.
The right way to fix this is probably to drop the img tag and use a CSS background url instead.

Prevent sending the binary each time.
Follow file input behaviour

There's not only one "login of a person", so it's better to show nothing
at all here.

we can delegate "editable", it's the default value of
my_view_mode_read_only_default_credential_question_answer

This category never existed and this is always logging:

    Base Category 'package_type' is missing. Accessors can not be generated.

Since catalog is migrated to an ERP5 document and can only be edited
with ERP5 UI we lost the hability to define security uid column for
default group, which is supposed to be defined with an empty string,
something like: `  | security_uid`.

Enable whitespace preserve on this field to allow saving this string
string without being stripped by formulator.

it seems de2545fc was supposed to be a
rename.

Otherwise indentation is lost when commit from erp5_vcs interface

Python scripts can be used as catalog methods, including as "clear catalog"
methods. This was causing error when upgradeSchema was called:

    product/ERP5Catalog/CatalogTool.py", line 1372, in upgradeSchema
      method_list_by_connection_id[method.connection_id].append(method)
    AttributeError: connection_id

tables() method of ZMySQLDA returns also views, which are not deleted
with DROP TABLE but with DROP VIEW instruction.

progress report shows an error like this:

![progress report page showing error 500](/uploads/6857ba9d8405d1bbba35b0857bc765d8/Screenshot_2020-04-17_at_18.04.03.png)

See merge request !1103

After discussing on
nexedi/erp5!1103 (comment 104474) we
amended the original commit so that if there are no bt to install at
this point we consider this step is finished (use 1 and not 0)

nexedi/erp5@71bde9ab (comment 104383)

It may not be the case if there is only one view, as defined by the hateoas spec

for Base_getDocumentScannerDefaultBackendDataAsJSON
since we need to be able to create Active Process

Add them to BaseAccessorHolder (like `Base Category` accessors) instead of
Base class so they can be regenerated on reset while not having to remove
ZODB Components from Base class on reset.

This means that providesIFoo() will only be available on Portal Type classes
whereas before it was working for direct Document instanciation, but the latter
has been banned for several years anyway and the few remaining ones have been
fixed (23b2b5fd, e791d08a).

Also, instead of Base.provides() being a CachingMethod() (does not work with
resets), create a method dynamically on the Portal Type class (erp5.portal_type.Foo),
as not caching at all is ~18 times slower.

And thus filesystem Interfaces were not displayed/selectable in BaseType_view.

erp5_certificate_authority: Certificate Authority Tool: All ERP5 objects *must* have have a Portal Type in Types Tool.

And remove hack in erp5_promise which was creating a non-Portal Type class of
portal_certificate_authority. Instead, add a depend on erp5_certificate_authority.
`providesI*` accessors are now in BaseAccessorHolder rather than Base due to ZODB
Components, this breaks reindexing (`AttributeError: providesIPredicate`).

This gets rid of:
  WARNING ERP5Type.dynamic Cannot find a portal type definition for 'Certificate Authority Tool', trying to guess...

This has been banned since the introduction of Portal Type class. When creating
a new ERP5Form via addERP5Form/ZMI, its MRO:
  * Before:
    <class 'Products.ERP5Form.Form.ERP5Form'>
    <class 'Products.ERP5Type.Base.Base'>
    ...
    <type 'ExtensionClass.Base'>
  * Now:
    <class 'erp5.portal_type.ERP5 Form'>,
    <class 'Products.ERP5Form.Form.ERP5Form'>,
    <class 'Products.ERP5Type.Base.Base'>,
    ...
    <class 'erp5.accessor_holder.property_sheet.SimpleItem'>
    <class 'erp5.accessor_holder.property_sheet.Folder'>
    <class 'erp5.accessor_holder.property_sheet.Base'>
    <class 'erp5.accessor_holder.property_sheet.CategoryCore'>
    <class 'erp5.accessor_holder.BaseAccessorHolder'>
    <class 'Products.ERP5Type.dynamic.portal_type_class.GetAcquireLocalRolesMixIn'>
    <type 'ExtensionClass.Base'>

Thus it was missing many accessors and was working only by chance (or at least
unless these accessors were not called until the object was automatically migrated
by the next call to __setstate__). Namely, as `providesI*` accessors are now in
BaseAccessorHolder rather than Base due to ZODB Components, this breaks reindexing
(`AttributeError: providesIPredicate`).

Also, remove hardcoded _getAcquireLocalRoles() now that it is not used as a regular
class anymore. Set this on the portal type object instead.

This gets rid of:
  WARNING ERP5Type.dynamic Cannot find a portal type definition for 'ERP5 Form', trying to guess...

km, content_translation, ods_style, open_trade, simulation and budget

See merge request !1094

Expanding frozen Simulation resulting from a split and Defer raise a `NotImplementedError`.

It comes from the `_extendMovementCollectionDiff` function in [RuleMixin](product/ERP5/mixin/rule.py) checking the recorded property "Quantity". The Quantity Split Solver set this variable to zero hence leading the function to consider compensation is needed. This merge request remove the setting of the recorded property `quantity` on the the split movement. Re-expanding from the root was also removing that recorded property asking the question if this is needed.

As of now system having used Split and defer Quantity will most likely not be able to re-expand their resulting simulation.

A Test is added to validate the fix.

See merge request !1097

Caching forever would produce wrong results after installing a business
template containing interfaces, using a transaction cache is enough
(actually it may not even be needed).

We were not considering interface without the I prefix for component
interfaces