ERP5Form : solve security issues with dymanic dialog Folder_viewSearchDialog

With a non manager user, the dialog was raising an UnauthorizedError
when accessing form properties like id or update_action.

With verbose security we had :
Unauthorized: Your user account does not have the required permission.
Access to 'update_action' of (ERP5Form at /erp5/person_module/Folder_viewSearchDialog)
denied. Your user account, [some account], exists at /erp5/acl_users. Access requires
one of the following roles: ['Assignee', 'Assignor', 'Associate', 'Auditor', 'Author',
'Manager']. Your roles in this context are ['Authenticated', 'Member'].

By looking further, this regression started with the introduction of erp5_hal_json_style
bt which install ERP5 Form portal type with "Acquire Local Roles" unchecked.

By looking also at aquisition chains of usual Form :

(Pdb) self.person_module.PersonModule_viewPersonList.aq_chain
[<ERP5 Form at /erp5/PersonModule_viewPersonList used for /erp5/person_module>,
 <Person Module at /erp5/person_module>, <ERP5Site at /erp5>, <Application at >,
 <ZPublisher.BaseRequest.RequestContainer object at 0x7f76305cae90>]

And at the one of Folder_viewSearchDialog:

(Pdb) self.person_module.Folder_viewSearchDialog().aq_chain
[<ERP5Form at /erp5/person_module/Folder_viewSearchDialog>,
 <Person Module at /erp5/person_module>, <ERP5Site at /erp5>, <Application at >,
 <ZPublisher.BaseRequest.RequestContainer object at 0x7f05f0751850>]

It seems fixing the acquisition chain is better option than allowing to Acquire Local
Roles on all forms. We now have following chain for this dialog:

After this patch, we have :
(Pdb) self.person_module.Folder_viewSearchDialog().aq_chain
[<ERP5Form at /erp5/Folder_viewSearchDialog used for /erp5/person_module>,
 <Person Module at /erp5/person_module>, <ERP5Site at /erp5>, <Application at >,
 <ZPublisher.BaseRequest.RequestContainer object at 0x7f76305cae90>]
Initial release of Implicit Item Movement, simple movements that can be used to have a movement from nowhere to the node where this item starts to be tracked
Movement: Add isMovingItem method to be possible check if the object is moving physically or not

erp5_mysql_innodb_catalog : Use isMovingItem instead of isAccountable to be possible index only movements that are moving physically

Movement: by default Movement should returns false. Otherwise it will index not expected objects in item table

erp5_mysql_innodb_catalog: check if there are movement items instead of aggregated uids
Simulation Tool: Extend getTrackingList to be possible pass transit states to the SQL query

Avoid pass next_item_simulation_state to _generateSQLKeywordDict because it will always ignore this parameter and display messages in logs

Add test to parameter with output=1 in getTrackingList method
erp5_item: Set current equal 0 by default to use getCurrentTrackingList instead of getTrackingList

With this, is possible see the destination of the Item shipped in the Tracking tab
erp5_item: Change listbox in Item_getTrackingList to sort by date and display time in the date column

In this way is easier to follow and check where is the item
testInvoice: add test to reproduce rounding issue when Accounting Transactions are created
erp5_accounting: Improve script to fix the rounding issue
testOrder: create default address in entities to not fail when call Invoice_viewAsODT to generate invoices
testInvoice: add more asserts to check if the total_price in the invoice is consistent with the Accounting Transaction line created