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

zarf connect on a headless system attempts to execute xdp-open on the system as an external dependency to the Zarf CLI and subsequently fails. The --cli-only flag circumvents this problem by attempting to open the default system browser. I believe the default behaviors should be switched.

See exec.LaunchURL()

Describe the behavior you'd like

• Given zarf defaults to encapsulated execution
• When zarf connect is executed
• Then it defaults to the --cli-only logic and browser automation is exposed with a flag separately

Describe alternatives you've considered

Remove support for launching the browser automatically and only support the headless output with associated tunnel link.

Additional context

I believe Zarf should always default to execution without requirements on external/system dependencies. This could mean flipping from defaulting to opening a browser to defaulting to the --cli-only behavior and expecting