standalone-tarball-tests is flaky

[mtardy]

See https://github.com/cilium/tetragon/actions/runs/11123370825/job/30906850837?pr=2955.

Sometimes we see:

sudo tetra status
  sudo tetra tracingpolicy list | grep bpf -
  sudo tetra bugtool
  test $(stat -c %a /var/run/tetragon/tetragon.sock) -eq "[6](https://github.com/cilium/tetragon/actions/runs/11123370825/job/30906850837?pr=2955#step:10:6)60"
  sudo tetra tracingpolicy add examples/tracingpolicy/tcp-connect.yaml
  sudo tetra tracingpolicy list | grep connect -
  sudo grep "tetra" /var/log/tetragon/tetragon.log
  shell: /usr/bin/bash -e {0}
Health Status: running
Error: Process completed with exit code 1.

Rerunning usually seems fine, but it would be better to have a reliable test.