ZODB Components: BusinessTemplate: On migration dialog, ignore source files not available anymore (ex: change branch).

Test should not depend on external websites, we already use erp5.com for
some other tests, so let's use it also for RSS.

/reviewed-on nexedi/erp5!1028

Deleting matrix cells with manage_delObjects is not a good solution, as
this breaks matrix index consistency.
Also, call isBasePricePerSlice rather than introspecting wrapped method
arguments - the only wrapped method is _setBasePricePerSlice anyway !
Also, explicitly trigger SupplyCell_updateSliceBasePrice as it depends on
isBasePricePerSlice value at line level, and it just changed, and cell-level
interaction workflow does not trigger on line changes.
Also, get rid of a trivial local variable.
Also, fix the exception expected from list.index .
Also, raise if multiple quantity criterion are somehow found.

When server replies with a non XML content type feeparser attempt to
parse anyway, but set the bozo flag.

https://universal-feedparser.readthedocs.io/en/latest/#handling-incorrectly-declared-media-types

If parsing fail because the feed is not a valid RSS XML stream,
feedparser fail in other ways, so we can safely ignore this error.

This should repair recent failures with testFeedReaderGadget now that le
monde changed configuration on their website:

     $ curl -sD -  -o /dev/null https://www.lemonde.fr/rss/une.xml | grep Content-Type
     Content-Type: text/html;charset=UTF-8

/reviewed-on nexedi/erp5!1027

See nexedi/erp5@b678a025

Introduce the object_jio_jump action category to mark all compatible actions.

erp5_xhtml_style supports object_jio_jump.

A correct redirection is needed to jump in both UI.

ERP5JS will display modules on the current document context,
as if the jump was instead a object_view action.

This improve the compatibility with ERP5JS

It will reduce the HTML size and prevent any browser parsing incompatibility.

ZODB Components: erp5_banking_core: Fix testERP5Banking{AccountingCancellation,BankAccountInventory,CheckDeposit} failures.

BankingOperation monkey patches several ERP5 basic classes to add getBaobab* methods.
With ERP5Banking Product on FS, BankingOperation was imported at Zope startup when
loading Products and monkey patches were applied.

Moreover, since this was added and because of a bug in bt5 implementation of
provide dependencies, it was not possible to install this bt5 from TemplateTool
on a fresh instance:
  [...]
    File "product/ERP5Type/tests/runUnitTest.py", line 417, in _installBusinessTemplateList
      with_test_dependency_list=True)]
    File "product/ERP5/Tool/TemplateTool.py", line 1200, in resolveBusinessTemplateListDependency
      return self.sortBusinessTemplateList(list(bt5_set))
    File "product/ERP5/Tool/TemplateTool.py", line 947, in sortBusinessTemplateList
      "Circular dependencies on %s" % reverse_dependency_dict.keys()
  NotImplementedError: Circular dependencies on ['erp5_mysql_innodb_catalog', 'erp5_banking_core', 'erp5_property_sheets', 'erp5_core', 'erp5_pdm', 'erp5_trade', 'erp5_accounting', 'erp5_core_proxy_field_legacy', 'erp5_simulation', 'erp5_base']

  -> erp5_banking_core depends on erp5_trade.
  --> erp5_trade depends on erp5_base.
  ---> erp5_base depends on erp5_full_text_catalog meta bt5 resolved to erp5_banking_core (provision_list).

This fixes testBanking* Unit Tests failures since ERP5Banking migration to ZODB
Components (0d2bd4c0) not triggered with FS Unit Tests because it does not try to
resolve dependencies and just install them in getBusinessTemplateList() order.

ZODB Components: Cosmetic: Remove Unit Test FS-only getBusinessTemplateList() now that it has been migrated.

ERP5Site: Do not override newContent() but use FolderMixIn implementation to have a consistent behavior.

ERP5Site was raising error when ID or portal_type was not passed but there is
no reason to do so (as it is done in FolderMixIn.newContent()). This allows
calling ERP5Site.newContent(temp_object=True) without ID, likewise Folder.

Folder: Allow to create temp_objects anywhere, without checking if it's in allowed types for that Portal Type.

Until now, creating a temp_object with newContent() required for the temp_object
to be in allowed types. However, this was inconsistent with (now deprecated)
newTemp*() functions (calling directly constructInstance()) not having such
limitations.

Besides lifting such limitation being needed to properly replace newTemp*() calls,
portal_trash.newContent() pattern is already commonly used used here meaning there
is a real use case.

This also fixes testBanking* failures: newTempCashDeliveryLine() created objects
on 'Cash Inventory' and latter call Delivery.isAccountable() which does not exist on
portal_trash.

See also 04b49859.

/reviewed-on nexedi/erp5!1025

Also hide seconds as it weights down the interface, and to follow the behavior of XML style

This is an empty modules whose names are dynamically inserted by
AccessControl.Implementation.

These constructors are not recognized by pylint and now we have
no-name-in-module errors.

Because since introduction of portal types as classes there was this
idea of deprecating those in favor of using newContent(temp_object=True,
switch to this new syntax.

Since we still have to create documents in portal_trash, only change the
minimal to get coding style tests passing again.

/reviewed-on nexedi/erp5!1024

for Person_viewAssignment form

For example, ExtensionClass (such as ValidationFailed) need to have their AST properly
generated. This fixes 'Use of super on an old style class (super-on-old-class)' error.

Besides of being needed for bootstrap, this also makes more sense than ignoring
completely ERP5Type as some modules should not be in there and should be migrated.

ZODB Components: Preparation of erp5_base migration from FS: LoginAccountProviderMixin implements ILoginAccountProvider (otherwise unused).