Major Description
In https://issues.couchbase.com/browse/MB-59364,
We found that config update in some scenario arrived from a past dead client and got applied to chronicle. The specific scenario was addressed as part of that ticket. This ticket is to analyze overall chronicle transactions in our code and close any gaps in that area that would be prone to stale config updates. We want to ensure transactions are done in such a way that we avoid applying stale config updates from the past. Generally we want to ensure that old config updates can't cause config corruption issues or leave the system in an undesired state.
