Add "cyctl helm migrate" command to batch-migrate Helm releases to Cyclops Modules

[0XSIKIPON]

closes #747

📑 Description

What this PR does / Why we need it

This PR introduces a new CLI command cyctl helm migrate to automate migration of existing Helm releases within a namespace to Cyclops Modules.
By running,
cyctl helm migrate --namespace <ns> --releases <release-name or list of releases> --repo <template repo> --path <template path> --version <version>
The system will :

• Validates the specified Helm chart template repo/path@version.
• Fetches values from all Helm releases in a given namespace.
• Creates Cyclops Modules using the template and Helm values.

✅ Checks

• I have tested my code (provide screenshots or screen recordings of a working solution)
• I have performed a self-review of my code

Before Migrating:

Run cmd to migrate helm release to Cyclops Module:

Migrated helm release to Cyclops Module:

Additional context

PR Type

/kind feature

[petar-cvit]

Thanks for the PR 🧡

I left a comment on reusing the Kubernetes client from cyclops-ctrl/pkg. Also, migrating the whole namespace at once sounds a bit risky. Can we require users to provide a list of releases they want to migrate?

[petar-cvit]

Can we use the Kubernetes client from cyclops-ctrl/pkg instead? This way, you don't have to reimplement the utility package

[petar-cvit]

Can you revert to the previous version of Go and other dependencies unless crucial?

[0XSIKIPON]

@petar-cvit Thank you for the feedback. I'll be working on the requested changes and push the refactored version.

[0XSIKIPON]

@petar-cvit I have made the required changes and updated the PR description, you can check again.