Single ZK node fate data

[kevinrr888]

Is your feature request related to a problem? Please describe.
For MetaFateStore, it would be beneficial to have all the data associated with a fate id in a single ZooKeeper node. This allows for atomic updates to a fate id. This will be slower than the current implementation. We are trading some speed for correctness. However, since this is only used for the tables in the accumulo namespace (ROOT, METADATA, FATE, SCAN_REF), this is a good tradeoff. In previous versions (before 4.x), MetaFateStore (aka ZooStore) was used for all transactions, so this change wasn't practical. With this change, it would also be nice to serialize the data as JSON allowing for easier serialization and deserialization and for better readability.

Additional context
#4524 (comment)
#4524 (comment)

[kevinrr888]

Another thing to note with this change is that we would also be able to have checks for expected statuses like UserFateStore can (and already does) do (for example, compare the differences between UserFateStore and MetaFateStores impls of delete()). This would give us the extra validation that UserFateStore has in MetaFateStore. Additional context regarding this can be found here #4242

This might be done in a follow on to this issue, or as part of this issue