feat: cassandra adapter to respect (or not) config for replication and other schema settings on create schema

[Lutherwaves]

Check Existing Issues

• I have searched the existing issues and discussions.

Problem Description

Currently after #107 is merged, cassandra schema creation hardcodes replication strategy. We should evaluate offloading this to config for more flexibility (or not)

Desired Solution you'd like

Something in the lines of:

• development.yaml configures the replication strategy as part of storage.config

Additional Context

#107 (comment)

[ayashjorden]

If we move the Keyspace creation into a migration file, then users may be able to specify their replication strategy of choice.
If we keep it as part of the CreateSchema funcion, then we need to add custom code that will handle (eventually) all replication strategies. surely we can start with SimpleStrategy (single datacenter) or NetworkTopologyStrategy (Multi-DC).

We need to gather requirements on how this functionality should look like. and what about modifying the replication strategy.

The fact that there are products on the market like Liquibase, makes me thing that magics storage "sell-point" is the simplicity and easy entry point.