Use full txn struct instead of just txn ID

Move from dealing with just transaction ID to using the full transaction
struct in write intents and in request / response headers.

Cleaned up some code in MVCC that was unnecessarily complex and introduced
concept of transaction epochs for Put() and for ResolveIntent(). Transaction
epochs start at 0 and are incremented every time a transaction is retried.
Transactions are retried (instead of aborted) in the event that a value is
encountered within the "window of uncertainty" between RequestHeader.Timestamp
and RequestHeader.MaxTimestamp, or in the case of an SSI transaction, if
the final transaction timestamp is not equal to the initial transaction
timestamp.

Typically, when a transaction has to restart, it covers all of the same
keys on writes and increments the intents' epochs accordingly. However,
if there's conditional logic in the transaction, it might end up skipping
some keys which were written the previous run--those earlier intents should
then not be committed when the intents are resolved after txn commit.
No because this is a common occurrence. Let's say a transaction looks like the following:

  if Read(a) == 1 {
    Write(b, 1)
  } else {
    Write(c, 1)
  }

If that runs once in SSI but ends up getting pushed, it will rerun; if on rerun, value of "a" changes to != 1 and we put down a different intent, we're going to have an intent from first run (epoch=0) at "b" and an intent from second run (epoch=1) at "c". We'll resolve both intents, but we want to actually resolve the intent with the non-matching epoch as though commit=false, so it's removed. Returning an error would leave this intent there instead of aborting it.