Single node META FATE data

[kevinrr888]

closes #4905

• Moved all the fate data for a single META transaction into a single ZK node
  • Pushed all the data into NodeValue (renamed to FateData)
  • Previously, FateData stored TStatus, FateReservation, and FateKey. Now additionally stores the REPO stack and TxInfo.
• Status enforcement added to MetaFateStore (previously only possible for UserFateStore).
• Moved testFateInitialConfigCorrectness() from UserFateStoreIT to UserFateIT
• Renamed UserFateStoreIT to UserFateStatusEnforcementIT (now extends a new class FateStatusEnforcementIT)
  • Now only tests status enforcement (previously status enforcement + testFateInitialConfigCorrectness())
• Created MetaFateStatusEnforcementIT (extends FateStatusEnforcementIT)
  • Tests that the new status enforcement in MetaFateStore works
• Created FateStoreUtil, moving the createFateTable() util here, created MetaFateZKSetup inner class here (the counterpart to createFateTable() for UserFateStore but sets up ZooKeeper for use in MetaFateStore)
• Deleted UserFateStoreITs (now UserFateStatusEnforcementIT) method injectStatus replacing with the existing setStatus which does the same thing
• Ensured sunny day and all FATE tests still pass with these changes

I did not end up using JSON for the fate data. I was not sure what the benefit of this would be since the data needs to be stored in ZK as a byte array anyways and it seemed simpler to me to just keep the same serialization/deserialization strategy for the fate data. Maybe this could be changed to JSON in a follow on if there would be a benefit of using JSON over the current strategy.

[keith-turner]

These changes look good. The test cleanup and reorg is nice. The only possible problem I saw was the repo ser/deser. Wondering if the ! char could occur in serialized data. Would be nice to avoid that.

[kevinrr888]

Addressed in 29edaa2:

• Got rid of END_REPO_DATA marker, replacing with simply writing the number of repos to read
• Avoid AtomicBoolean in MetaFateStore.FateTxStoreImpl.push(repo) by changing StackOverflowException to instead be a RuntimeException (previously Exception)
• Deleted unnecessary preexisting catch and immediate re-throw of a StackOverflowException in MetaFateStore.FateTxStoreImpl.push(repo)
• Cleaned up and refactored MetaFateStore methods which mutate existing FateData; now reuse same pattern across these methods: all call new method MetaFateStore.mutate()

[kevinrr888]

Resolved the conflicts from the recent seed transaction speedup. Thankfully, those changes were mostly for UserFateStore and these are for MetaFateStore, so conflicts were very easy