Release Cadence With Pre-release

[TheDarkula]

Currently, helm chart releases are using a pre-release version of the ziti binary.
I feel that there needs to be clarity as to what is included in a stable helm chart release.

[qrkourier]

I agree it's time to adopt upstream Ziti's notion of a stable vs. prerelease. From now on, OpenZiti Helm Charts will have a default app version of the latest stable release of upstream Ziti binary.

For example, if upstream Ziti increments the latest stable release 1.2.3 to 1.3.0 by marking the 1.3.0 version as "not a prerelease" in GitHub, then the next Ziti Controller Helm Chart will pin default appVersion 1.3.0.

[qrkourier]

@TheDarkula I will make the exception to pin default Ziti app versions in the controller and router charts with latest patch versions of Ziti, because those represent bug fixes, until the next upstream stable increment is marked. Then, I will begin to implement the new policy of adopting only stable releases as the default app version in Ziti Helm Charts.

Additionally, The Ziti Controller and Ziti Router Helm Charts will begin to have default Ziti app versions of the same vintage to maximize the probability they are compatible. This means that, when the Ziti Controller chart adopts a breaking change, the Ziti Router will adopt it at the same time, giving consumers the ability to handle potential breaking changes by merely upgrading to the latest chart version.