1. Add a column family meta to store metadata about the DB
2. Add a field SCHEMA_VERSION in that CF, which tells us which version the database is
3. If the compiled version doesn't match the version in the db, return with an error

Generally, it seems to be a bad idea to allow running an old Chronik version on a new database, unless we define some clear stability guarantees.

The current behavior is very strict, where the version has to match exactly, to prevent invalid states where e.g. the txs in the database are at a different height than the blocks.

Newer Chronik versions could always be more relaxed, and/or allow upgrading the existing database without reindexing.

ninja check-crates, also all the chronik_* functional tests