Needs more tests.

This reverts commit 74db4d39.

This is not a new feature, this behavior is compatible with the old caching
implementation that was using inventory_stock table.
In other words, this brings backs the backword compatibility in invetory
caching.

omit_balanced_accounts was always displaying 1
omit_empty_accounts should not exist

To display the list of possible accounts we include validated nodes and  nodes that have been previously used on accounting movements. We include 2, because we want the user to be able to issue a report on a node that has been used in the past and is now invalidated.

The problem with this approach is that such query is very slow, when there are a lot of Movements.

Then, with the commit only validated accounts will be considered

This commit is part of 0ee6eae7.

The script ERP5Site_getWorkflowStateItemList that receives the portal type and the state variable (simulation_state/validation_state) as parameters and it will returns the states for the workflow chained to the portal type

Only prevent ZODB Components to be validated as the source code cannot be
checked. This does not prevent BT to be upgraded, so this should be ok.

for filter empty content_translation dictonaries in vcs

* imap.mail.ru and imap.gmail.com use '/' as a delimiter.
* gmail.com does not support '( ALL )', use 'ALL' instead.
* parse multiple flags.

Before:

default_inventory_calculation_list = ({"inventory_params" :
                                        {"node" : self.getDestination(),
                                         "group_by_sub_variation" : 1,
                                         "group_by_variation" : 1,
                                         "group_by_resource" : 1,
                                         }
                                         ..

After:

default_inventory_calculation_list = ({"inventory_params" :
                                       {"section": self.getDestinationSection(),
                                        "node" : self.getDestination(),
                                        "group_by_sub_variation" : 1,
                                        "group_by_variation" : 1,
                                        "group_by_resource" : 1,
                                         }
                                        ..

This is because Inventory_view of erp5_trade has both 'section' and 'node'
fields, so users can input both values, but due to the old default parameter,
the section will be ignored for inventory indexing. This is inconsitent.

Selection: Do not set Selections if the new and store name differs instead of raising AssertionError.

In Live Test, setUpOnce() is not called, instead afterSetUp() should be
used. Also, remove update of Local Roles as this is already done automatically
upon bt5 installation since a481170a.

ZODB Components: When executing code, module globals disappeared after a reset performed in another thread.

This fixes failures in erp5_configurator* tests where BTs installed during the
tests trigger a reset and globals (such as DateTime global import) were reset to
None.

runUnitTest: Test the full ports range as some tests require Zope to listen on a port (testShaDir...).

With erp5testnode, many tests are running concurrently on the same machine and
only 3 ports were randomly tested before continuing and thus not listening to
any port. Moreover, checking the full range (500 ports) takes less than 1ms...

Therefore, all Test Components are now ERP5TypeLiveTestCase. For backward
compatibility sake, just modify Test Component class bases to
ERP5TypeLiveTestCase, likewise runLiveTest.

This means that tests ran through runUnitTest and from Live Tests ERP5 UI would
behave exactly the same, contrary to the implementation before Test Components.

Also, move a method called in one of ERP5TypeTypeMixin method from
ERP5TypeTestCaseCommandLine.

ZODB Components: Revert 'Allow to execute runUnitTest for bt5 Test Components' (a771dca4) to fix tests bootstrap.

The new syntax to load ZODB Tests Components is:
runUnitTest BT_TITLE:TEST_NAME

That commit was too adhoc as it was relying upon filesystem to load Tests
Components and was not behaving like any other Components (versions was not
available and other Components were not importable).

At the end, it would have meant that a Test Component ran through runUnitTest
and Live Tests (in ERP5 itself) would have behaved differently, thus instead:

1/ Install BT_TITLE dependencies and its test dependencies (new bt property to
   specify bt to be installed only for tests on a fresh instance).
2/ The site is loaded.
3/ Load the test by importing it like any other Components.

Avoid an extra step for developers by keeping the last Workflow History for
Components by default.