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

zarf connect does not expose all of the capabilities of kubectl port-forward. Specifically I would like to be able to specify the listen address for a zarf connect so I can bind to more than just 127.0.0.1

Describe the behavior you'd like

• Given A zarf package is deployed with a connect label
• When zarf connect <package> --address 0.0.0.0 is ran
• Then a kubectl pf is created that binds to all interfaces