Generally allow customer to repay payment. The work was based on:

 * Start date do not have to be set during building.
 * Allow to reuse existing ID and allow PayZen to inform user, that transaction
   is already registered.
 * Do not create too many ids.
 * Drop not needed logging.
 * Be as precise as invoice's currency.
 * Consider all planned or confirmed transactions and take actions based on
   transaction status.

Do not kill the client browser.

Sleep is bad, but better than destroying all components.

It is only used in vifib_web

This will ease maintainance.

Default script from erp5_crm already provides needed functionnality to support
anonymous user.

vifib_crm can be dropped as it becomes empty.

(cherry picked from commit fc0e4e18)

Conflicts:

	master/bt5/vifib_base/bt/revision

Try to show interesting information about deliveries which are not solved.

Delivery with solved state.

In order to minimise amount of non merged documents build each combination of path
and (closest) explanation in one shot and lock this building.

Note: As it is impossible to create AND-ed transaction level lock SimulationMovement_buildVifib
method is "unsafe" to be called in separate transactions.

Deliveried, expanded and solved subscription packing list.

This is: planned and solved payment.

User has posted invoice and planned and solved payment.

It is now available and gives better results than uid sort.