Revisit and bump policies to 1.X.Y

[viccuad]

A bunch of policies have a semver of 0.X.Y. We consciously picked semver 0.X.Y for policy version as that means that the policy API (in this case the policy spec.settings) is not considered stable. But to be fair, we haven't had the need to revisit this after years, and several policies have gotten minor releases, with none breaking backwards compatibility.

Maybe it is time to showcase this commitment by bumping them to 1.X.Y.

Acceptance criteria

• Bump and release versions 1.X.Y for those policies that are considered stable. See here for list of policy repositories and their maturity level. Consider bumping from 0.X.Y to 1.X.Y instead of 1.0.0 for easy bookkeeping.

[viccuad]

Note: there's the possibility of having an ABI break for the policies (their Wasm validate and validate_settings functions for example), and needing to rebuild all their Wasm modules. This of course would warrant a major version bump of Kubewarden. We haven't performed such a thing, nor we intend to do so any time soon.