erp5_administration: Add Scripts for Alarm to update validation state according to consistency state

    If two open orders are validated on the same transaction, archivePrevious script will get the an already archived as catalog will be outdated.

   This allow the administrator define which Login portal types are searched.

Also extend tests to cover recently changes

   This is an alternetive way to login using Certificates. Probably this format
   will evolve into use caucase;  however this only introduce some most basic features.

   Use Certificate Login for store login definitions

  Please squash me in future.

  If the user wants actitivites, it should create multiples StandardBT5ConfiguratorItems,
  This should accellerate Tests based on ERP5Configurator.

  This should be recoded, but it should speed up bootstrap of a site,
  as get modified objects are not called.

It the user don't have fully permission on the object (already changed state), this set will fail to check if source should be defined.

  The upgrade ordering seems buggy and requires to force reinstall it

This allow during a subscription process, create a user and them create all
documents using that user w/o rely on proxy roles (keeping good ownership
across the documents).

Without this (on slapos master ui) the redirection places value unquoted causing parser to fail later on when resolve {n.me}

  The user can be present from diferent logins, password tool only works with ERP5LoginUserMager
  users.

Mixed commit:

  43b1ae1b
  2f05fe1b

Returning true allows to add movements to existing one, and this group shall
always separate them.

Note: Generic code shall have no constraints at all.

Conflicts:

	bt5/erp5_accounting/bt/revision

If 2 lines have the same effective date (catalog has a 1 second precision),
always return the validate and open first.

Commit: 02d06501

Changes applied from history:

http://git.erp5.org/gitweb/erp5.git/history/refs/heads/interaction-drop:/product/ERP5/Document/SubscriptionItem.py?js=1

Original commit from : Lukasz Nowak <luke@nexedi.com>
                       3e45ec35

Conflicts:
	bt5/erp5_crm/bt/revision

See merge request !1480

See merge request !1479

See merge request !1477

    This allow including more items to be ignored, preventing diffs from pure development.

  Those 2 exceptions are from SlapOS Master codebase, and for now we cannot remove it.

  Rather them complexify the ignore lists, we are hardcoding the values for minimase the ignore list
  to the least entries as possible.

  This is required for multiple sites support and allow us write unit tests and not create a 100 lines mock.

   Whenever used via activity nodes, it is not possible to discover IP of the server via portal absolute url.

See merge request nexedi/erp5!1478

   Only Person could include getFirstName and getLastName, so implement a fail-safe in case Login is inside a Computer or any other document.


(cherry picked from commit f7694fbc)

  Ignore list is useful when you have old business templates in production (used to include data for example) and test business templates on test environment (ie;: erp5_test_ui_core).

  This allow us control the 'dump to assert' changes easily.

OSOE website is not necessarily part of standard configurator so only adjust if it is indeed installed.

See merge request nexedi/erp5!1476

(cherry picked from commit 1ad44735754d1701ffb12fecbb641602bfd01c8a)

Suite

Module erp5.component.document.erp5_version.ERP5ProjectUnitTestDistributor, line 326, in getTestSuiteSortKey
  wanted_test_core_quantity = PRIORITY_MAPPING[test_suite.getIntIndex()][1]
AttributeError: getIntIndex

Avoids the infamous 1024 file descriptor limit. No functional change
expected, as it seems unlikely this bug ever triggered on waitress-managed
file descriptors.