In case there is a breaking change in pgroll, the CLI should detect it and fail as early as possible (so that it doesn't accidentally corrupt any state in the case of a breaking change).

Proposal

Store the version of pgroll CLI with pgroll init and in the case of a breaking change, detect the version in database and fail early.
(pointed out by Carlos) This is tricky in case there is a regression, pgroll init storing state might stop the user from downgrading the CLI.

Potential solutions:

• we maintain a compatible versions map and up / downgrading works unless the version boundary is crossed.
• we only show a warning and/or a confirmation dialog and let user override.

Related #765