Zarf cli sometimes hangs on k8s jobs waiting for status 'Running'

[snowping]

Environment

Device and OS: Linux Arch
App version: Zarf version v0.49.1
Kubernetes distro being used: k3s

Steps to reproduce

1. Add a kubernetes job with a tiny script (tested together with datainjection initContainer)
2. Deploy it

Expected result

Zarf cli does accept both "Running" and "Succeeded" as status to continue (deployment vs. job)

Actual Result

In some situations, probably when a job pod has status "Running" only for a short period of time, zarf cli is waiting for status 'Running' but the pod/job has already status "Succeeded"

Visual Proof (screenshots, videos, text, etc)

See the following example debug log (repeated until timeout):
{"time":"2025-03-10T22:26:09.664680879+01:00","level":"DEBUG","msg":"checking pod for Running status","pod":"nexus-post-install-ltvbc","status":"Succeeded"}

Severity/Priority

It's blocking to upgrade to newer zarf versions when we use zarf with small k8s jobs.

Additional Context

see also slack discussion: https://kubernetes.slack.com/archives/C03B6BJAUJ3/p1741640794952949?thread_ts=1712075949.905459&cid=C03B6BJAUJ3