Update version to v0.22.2

[Shariatj]

Releasing a new version of Kubeaudit for the depracation notice.
Related issue:#593 (comment)

[jacobmichels]

In the interest of maintaining a clean commit history, would you mind squashing these commits into one?

[jacobmichels]

Does bumping this version automatically trigger a GH release once merged to main? Or is there a separate process for that

[Shariatj]

Does bumping this version automatically trigger a GH release once merged to main? Or is there a separate process for that

No we have to manually relaese it by creating a tag, ref: https://github.com/Shopify/kubeaudit/blob/main/docs/release.md

[dani-santos-code]

q: shouldn't this be a patch bump? we're not introducing new functionality and it's backwards compatible

[Shariatj]

Since this isn't a bug fix, adding a deprecation notice (considered a minor update without breaking functionality), I thought the next version should be v0.23.0. Could be changed to a patch bump too

[Shariatj]

@dani-santos-code changed it into patch bump now.

[dani-santos-code]

yeah, it's not a bug fix. It seems debatable, though. 😬 Found some discussions on StackOverflow around this and I don't see a clear consensus:

• https://stackoverflow.com/questions/52373074/how-to-semver-versioning-documentation-update
• https://docs.spryker.com/docs/dg/dev/architecture/module-api/semantic-versioning-major-vs.-minor-vs.-patch-release.html#what-is-a-major-release

[dani-santos-code]

This is not a blocker at all

[dani-santos-code]

lgtm! can we update the title of the PR? thanks!