cli: store kubernetes version as strong type in config

[elchead]

Context

Storing the K8s version as validated type saves a lot of parameter passing and centralizes the validation logic

Proposed change(s)

• store K8s version as weakly validated type (ignoring patch version) in the config
• allow to specify K8s version without patch (e.g. 1.27) as valid config value and resolve the patch version
• allow to specify a patch version in config generate (e.g. 1.27.4)
• add more unit test cases

Related issue

• AB#3374

Checklist

• Update docs
• Add labels (e.g., for changelog category)
• Is PR title adequate for changelog?
• Link to Milestone

[netlify]

✅ Deploy Preview for constellation-docs canceled.

Name	Link
🔨 Latest commit	bff1570
🔍 Latest deploy log	https://app.netlify.com/sites/constellation-docs/deploys/650971797e787a0008d91112

[elchead]

Discuss: supporting versions without patch as K8s version might be worth putting in the release notes

[elchead]

ran
E2E upgrade: https://github.com/edgelesssys/constellation/actions/runs/5998073530
E2E sonobuoy: https://github.com/edgelesssys/constellation/actions/runs/5999162031

[elchead]

@derpsteb I reverted the support for no patch specification in the config due to complicated case handling. I think it's not worth to support it, but have saved the stash if we decide to do so in the future

[github-actions]

Coverage report

Package	Old	New	Trend
cli/internal/cmd	56.30%	55.00%	↘️
cli/internal/helm	49.40%	49.50%	↗️
cli/internal/kubecmd	58.00%	58.00%	↔️
e2e/internal/upgrade	[no test files]	[no test files]	🚧
internal/config	79.80%	80.10%	↗️
internal/config/migration	[no test files]	[no test files]	🚧
internal/versions	13.90%	8.20%	↘️

[elchead]

Coverage report

Package Old New Trend
cli/internal/cmd 53.60% 53.40% ↘️
cli/internal/helm 47.70% 47.80% ↗️
cli/internal/kubecmd 57.70% 57.30% ↘️
e2e/internal/upgrade [no test files] [no test files] 🚧
internal/config 79.70% 80.00% ↗️
internal/config/migration [no test files] [no test files] 🚧
internal/versions 13.90% 8.10% ↘️

What's interesting about these metrics is that it doesn't encourage to test closer to E2E. I.e, the added test cases for the valid Kubernetes flag values in config generate do not add to the test coverage because it exercises code from the versions pkg. Would it be useful to also have a global coverage metric?

done

done

[elchead]

@3u13r can u give it another look pls when u find a moment?

[3u13r]

One small nit, otherwise LGTM