Introducing Schema Versioning for Recon Derby table to Handle Fresh Installs and Upgrades

Currently, Recon does not have a schema versioning mechanism in place for handling database schema evolution. As a result, when new schema changes are introduced (e.g., adding new enum states like MISSING, NEGATIVE_SIZE in the UnHealthyContainerStates) for the UnHealthyContainerTable, it becomes challenging to distinguish between fresh installations and upgrades, leading to issues where old schema versions may still be used despite an upgrade.

This ticket proposes introducing a schema versioning system to manage database schema changes in a more controlled manner