Untangle Zarf connect command

[AustinAbro321]

Is your feature request related to a problem? Please describe.

The Zarf connect command is confusing because flags can be set that conflict with the arguments.

For example, zarf connect doom --name=dbz --remote-port=9001 --type=svc --namespace=other-world is a valid command even if the service labeled with zarf.dev/connect-name: doom has nothing to do with the flags given because the options are ignored when a target is given after zarf connect.

Zarf connect should still have these flags, for now as to not cause a breaking change, but they should be deprecated and hidden.

Zarf should introduce a new command zarf connect resource and it should have required flags name, namespace and remote-port. As well as an optional flags type which defaults to svc and local-port which defaults to a random available port.

Describe the solution you'd like

• Given I have a svc called doom in the dos-games namespace serving on port 8000
• When I run zarf connect resource --name doom --namespace dos-games --remote-port 8000
• Then my browser is opened to a random local port on my local machine.