CLI should not exit with code 0 when there was an issue

[fharper]

Which version of kubefirst are you using?

2.3.3

Which cloud provider?

None specific

Which DNS?

None specific

Which installation type?

None specific

Which distributed Git provider?

None specific

Which Operating System?

macOS

What is the issue?

The CLI exit code is now always 0, even when the command didn't work properly. It is preventing automation using the exit code.

In that case, the exit code should be non-zero, usually 1. It wasn't an issue prior to the CLI revamp. I also assume it is like that for all commands, not just the create one.

Code of Conduct

• I agree to follow this project's Code of Conduct

[fharper]

This issue is really problematic if you do any kind of automation using the kubefirst CLI.

[fharper]

To reproduce easily, just create a gitops repository in your personal account, and try to create a k3d cluster. The preflight checks will fail because of the repository already existing, and the code returned will be 0, when it should be anything other than 0 since the command wasn't successful.