Feedback wanted: Consumer-controlled transactions

[PixievoltNo1]

This package already does transactions, in the sense that everything that changes in between tick resolutions gets batched up into a single set call to extension storage. Is there any demand for transactions that start and end when you want them to?

A possible API for this would have a new transaction method on the store group object, which returns a transaction object. The transaction object would have a stores property much like the one for store group objects, and a commit method that saves all changes to extension storage.