Maintain multiple k8s versions

[shinebayar-g]

I'm currently packaging only the latest k8s version (1.32 as of today). However, it would be better if we shipped all the supported versions as of today.
k8s-1.32
k8s-1.31
k8s-1.30

• Utilize npm dist-tags. E.g npm install --tag 1.31, npm install --tag 1.32 etc. Patch level can be omitted for brevity.
• New release versioning structure @k8skonf/[email protected].<build-number> Use upstream k8s minor version as a base and replace patch version with k8skonf build version. Because npm doesn't support build version of semver. [QUESTION] semver: Why is "+build" information ignored when "-pre" information is allowed npm/cli#1479
• This also means, supported k8s versions will be maintained as a subdir in the repository.