Remove the requirement that the keyspace must exist prior to running migrations

[efenderbosch]

FEATURE / ENHANCEMENT

Outcome Desired

Remove the requirement that the keyspace must exist prior to running migrations.

This could be accomplished by storing the cassandra_migration_version table in a separate metadata keyspace and adding a keyspace column so that migrations for multiple keyspaces could be tracked in the same table. This would allow users to start w/ a fresh Cassandra install and have a CREATE KEYSPACE IF NOT EXISTS ... statement in their baseline cql file.

Alternative solution:
Add createKeyspace/replicationStrategy/replicationFactor command line arguments and/or properties to optionally create the keyspace prior executing the migrations.

Additionally a JUnit Rule to use in tests would be very handy.

---

Definition of Done

The migration tool runs correctly without the requirement that the keyspace already exists in a CI/CD pipeline and can be utilized in integration tests using an embedded Cassandra instance.

---

Out of Scope

n/a

---

How to Demo

Start with a fresh install or embedded instance of Cassandra and use the migration tool to create the keyspace and other tables from scratch.