This makes code simpler, faster and easier to understand.
It is easy to forget that ZODB connections can be reused by different threads,
which led to bug such as the one fixed by commit 2c11b76a.

ZODB already maintains a pool of connections to reuse
so we don't need anymore to have one.

getSimulationQuantity/Source/Destination..
getOrderQuantity/Source/Destination...
getDeliveryQuantity/Source/Destination...

Those methods were not used and were calling some non existing ZSQL Methods
XXX wrong ! getSimulationQuantity is used !

doc.isMemberOf('') is not valid

getDefaultTotalPrice getSourceTotalPrice getDestinationTotalPrice

In inventory API queries, stock table is already selected, and we want the query parameters to be applied on this stock table, whereas default related keys would add stock table one more time

- add payment_request
- also index non accountable movements

to get rid of movement table dependancy

tickets are also in delivery table

InventoryListBrain does not need a getQuantity method which returns something
else that the total_quantity on this brain, this is just confusing (and using
movement table)

The idea is to use Inventory API instead.

Also, movement with 0 price where ignored by omit_asset_increase /
omit_asset_decrease
Signed-off-by: Aurélien Calonne <aurel@nexedi.com>

Signed-off-by: Aurélien Calonne <aurel@nexedi.com>