🐛 After Dictionary Migration, other instances of this service are not updating to the new dictionary

[joneubank]

Describe the bug

In an environment where there are multiple instances of the clinical system running, if a dictionary migration is performed successfully, then the "current dictionary" should be updated to the new dictionary version. The instance that performed the migration correctly reports the new version, but any other instances in the network do not.

Steps To Reproduce

1. Run multiple instances of argo-clinical connecting to the same DB
2. Run a dictionary migration using one of these instances
3. Call GET /dictionary on both running instances

You will see the instance that performed the migration reports the new dictionary version, while the other instance does not.

Expected behaviour

Both instances should report the dictionary version of the dictionary that was migrated to.

Suggested Solution

The current active dictionary state needs to be held in the database in a way that any running instance can query to report the current state of the clinical data system.

Currently the "current dictionary" is determined at startup and then never checked vs the database again.

[joneubank]

Until this is fixed, the inconsistent state between instances can be resolved by restarting all instances after a migration completes.