Given an existing cluster, is there any way to check
A) whether a local registry is enabled for that cluster, and
B) the value of registry-port/registry-name?

Relatedly: given a cluster that was started without the --enable-registry flag, is there any way to enable the registry post-facto?

Some clusters can be stopped when k3x is started. Users could think the current cluster should be ready, but they would really need to "start" it. We should show a warning saying something like "the current cluster is stopped".

What happened:
I ran:
kconnect use eks --region us-east-1 --non-interactive
Note: I had username, password, and IDP settings in config

I was then prompted for role arn

What did you expect to happen:
For kconnect to fail immediately, and to show that roleArn is required

How to reproduce it:
Run kcoonect use eks with all parameters required except --roleArn, and with --no