Let activity system to choose what and when shall be executed.

Thanks to this a lots of unindexObject will be grouped.

This is cheap operation.

Use catalog, as contentValues dies on big modules.

Show the speed of invocation.

As reindexation is not scalable delete before reindex and then
delete again just for sure.

Thanks to packet_size and activity_count it is possible to limit to one
small transaction per module.

Catalog can be used, as pervious step catalogs everything.

Also mark 04_ERP5Site_deleteVifibAccounting as not implemented.

A lot of documents are really huge.

Install configurator.

This BT5 can affect running site, so use them in test.

Do what user said and *exactly* what he said.