Idea for tracking database features

Currently we use Dao::getDbVersion to see what version of the database we're using.
This is a call to the database done at point of use, which is sometimes in a loop.

We're also getting more complex with our feature support/flags/etc.

A though just occured to me that to be able to pickup new available features (e.g. we program them but against a dev version of the database and then later updated the product database) we could have a background task that periodically checks the database for version/feature changes and sets the appropriate variables.

This would also make it easier to determine appropriate usage if we move beyond a single back end data store without nearly as much disruption.

Start with Dao::getDbVersion and trace its callers, especially uses inside loops, to understand the current version checks. This issue is complete only after a concrete design is agreed for background database version and feature detection; no implementation files or tests are named.