refactor: registry release CLI

Why

Refactoring the CLI seemed to be the fastest and most efficient choice after several months of not looking into the code. While getting back to fixing issues, I noticed that there was an underlying design fault which was pretty much the root of several failures. This may not be leaning on our iteration value, but the overall idea that we iterated previously remains.

Testing

I had the chance to set up a similar release flow on test projects and it was successfully creating releases that require manual file changes and also triggering the dependency bot.

Fixes

We should be verifying that the following issues are fixed:

• ci: k8s-workloads version bump automation is br... (#882 - closed)
• ci: CNG version bump automation is broken (#881 - closed)

Notes

• Requires the setup of a $REGISTRY_PATin CI Variables, with a read_repository permission
• I removed the release CLI issue logic since the focus is first to make sure we can release successfully