Almost working test, Inventory API still does not process properly.

Had I not done that before? How did it worked? Weird. Maybe just changed the configuration on the Portal Type ?

I am unsure if they should not instead be in the delivery movement group, that way we might be able to discard my change to ERP5Site and get rid completely of this inventory movement thing.

This fixes a regression with 445e8fa8 (ERP5TypeTestCase: rework
default manager password generation, 2024-05-27), it was no longer
possible to run live tests from a "normal" zope instance, this was
failing with:

Traceback (most recent call last):
  File "./eggs/Zope-5.10-py3.9.egg/Testing/ZopeTestCase/PortalTestCase.py", line 59, in setUp
    self._setup()
  File "./parts/erp5/product/ERP5Type/tests/ERP5TypeLiveTestCase.py", line 156, in _setup
    self.login()
  File "./parts/erp5/product/ERP5Type/tests/ERP5TypeTestCase.py", line 290, in login
    return PortalTestCase.login(self, user_name)
  File "./eggs/Zope-5.10-py3.9.egg/Testing/ZopeTestCase/PortalTestCase.py", line 146, in login
    user = user.__of__(uf)
AttributeError: 'NoneType' object has no attribute '__of__'

It was only possible from a runUnitTest instance.

Also: add `getTotalQuantity`. Why?

…and delete unused `z_catalog_stock_list_without_delete_for_inventory_virtual_movement`

In order to have Inventory Offset Lines, we want the user to be able to check
the generated lines before validating. This commit therefore adds an
intermediate state `planned`, which will be used to trigger generation of
Simulation Movements and building of the offset lines.

Some other small changes have been done to make the actions' names more clear
and adhere to ERP5 standards, but all keep backward compatiblity: previous states
have been kept, and previously validated inventories are now recorded so that
no Simulation Movements will be generated that would impact stock values.

See merge request nexedi/erp5!1963

   The script is supposed to be called on portal context (or any context) and not on MailevaSOAPConnector, and it should return a MailevaSOAPConnector for a given reference.

    In the implementation where the user cannot directly insert holidays (by an specialised role/implementation) it allow the accountant insert the values more easily. Using a simple action.

    Add simple jump for navigate to the holidays/leave

  This helps to review value on the print out