Monorepo versioning

[BohdanPetryshyn]

Context

By the time this issue is created, there're two packages in this monorepo:

1. Basti CLI (basti)
2. Basti CDK (basti-cdk)

Suggested versioning strategy

1. basti and basti-cdk are both versioned independently following semantic versioning.

2. A new major version is released in two cases

   1. The user interface has changed. For example, a basti-cdk property or a basti CLI option has been renamed.
   2. Basti CLI init command or basti-cdk infrastructure is no longer compatible with the existing versions of the Basti CLI connect command.

3. Newer versions of Basti CLI must support connecting to any older minor and major version of the infrastructure.

4. basti connect command checks if the infrastructure was initialized with the satisfying major version of Basti CLI or Basti CDK. If not, the user is asked to update to the latest version of Basti CLI (which must support the newer infrastructure).

[BohdanPetryshyn]

We can postpone the version checks implementation until the first infrastructure breaking check is introduced.

[BohdanPetryshyn]

Anyone with experience in publishing indirectly-depending packages from a monorepo is very welcome to share their thoughts on this 🤗