Implement three different transaction modes for ItemSync: single transaction (that's what we had until now), block-wise transactions (only available when using item streaming) and no transactions at all.

Since these basically represent tradeoffs between quick UI updates, runtime costs and to some extend data consistency we probably need this choice to select the best one for every usage of ItemSync.

This also uncovered a race in sub-job scheduling which could cause deadlocks.