SAT: Syntactic validation of catalog update for backward compatibility

[sherifnada]

Tell us about the problem you're trying to solve

Context is here.

We want to prevent backward incompatible connector changes by running a dedicated test suite on SAT.
Backward incompatible changes can happen on catalog change of a connector. We want to add tests on the discover command to ensure the changes made to a connector are backward compatible with the previous connector version.

Acceptance criteria

Acceptance tests should fail if one of this situation occurs:

• additionalProperties is set to false (already covered by SAT: all additionalProperties fields must be set to true #14878)
• An existing stream property’s type has been changed: we could allow for type expansion, but @sherifnada suggested first being conservative by disallowing any type change.
• A stream was removed/renamed

This work can be considered as an iteration upon #15194

[alafanechere]

grooming note:

• use semver to decide if breaking changes are allowed
• access connector status from SAT to bypass strict test for alpha (decide on what to do for custom connectors) : if a previous connector version is alpha anything goes.

[alafanechere]

access connector status from SAT to bypass strict test for alpha (decide on what to do for custom connectors) : if a previous connector version is alpha anything goes.

Created #15407

[alafanechere]

use semver to decide if breaking changes are allowed

Created https://github.com/airbytehq/airbyte-internal-issues/issues/789