cli: move cli/internal libraries

[msanft]

Context

We want to transition to a Constellation library that can be consumed by both the CLI and the Terraform provider. The CLI should only contain code that directly interacts with the user and should consume everything else through the library's API. A first step towards this is moving the packages that do not fall under this category from cli/internal to internal.

Proposed change(s)

• Move all packages from cli/internal to internal that will also be used by the Terraform provider.
• Create the internal/constellation package.

Additional info

• AB#3544
• E2E Test

Checklist

• 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	28fc5a9
🔍 Latest deploy log	https://app.netlify.com/sites/constellation-docs/deploys/655cb2d0f0c99e0008f3d887

[daniel-weisse]

Annotated some files of packages I think should be kept in cli/internal.

While we are already in the process of moving files, should we consider moving the Helm charts to their own (more globally visible) directory similar to the Terraform files?
I feel that it can sometimes be a bit of hassle to have them deeply nested somewhere in our Go helm code.

[github-actions]

Coverage report

Package	Old	New	Trend
cli/internal/cloudcmd	68.40%	68.40%	↔️
cli/internal/cmd	54.60%	54.60%	↔️
cli/internal/libvirt	[no test files]	[no test files]	🚧
cli/internal/terraform	72.30%	72.30%	↔️
hack/gocoverage	59.20%	59.20%	↔️
internal/constellation	0.00%	[no test files]	🚨
internal/featureset	0.00%	[no test files]	🚨
internal/helm	0.00%	54.30%	🆕
internal/helm/imageversion	0.00%	[no test files]	🚨
internal/kubecmd	0.00%	64.60%	🆕
internal/state	0.00%	94.60%	🆕

[3u13r]

LGTM