Redo capture writes to have a limit and a ordering. Also write captures seems to only capture 1 column.

[alee-r7]

Capture writes was built to capture all write requests for a given org. It has proven valuable for debugging and replaying data though we need to redo a little of it to make it easier to work with.

1. Cap the number of captures. Reason being this could be easily abused and explode if users aren't properly managing their capture.
2. Currently the first thing it captures in the list is by transaction id which doesn't have much value for replaying. You'd want to list by date first. Doing this you'd know the order of operations which is important.