fix(transparent-proxy): prioritize IPv4 executables initialization

[bartsmykla]

Improve IP-related initialization by first setting up IPv4 executables to determine the iptables type (nft or legacy). IPv6 initialization now occurs only if IPFamilyMode is set to DualStack, an IPv6 local address exists, and adding the ::6 address succeeds. This approach prevents failures in environments like Minikube, where nft is unavailable and IPv6 is unsupported, ensuring the correct selection of executables without errors.

Checklist prior to review

• Link to relevant issue as well as docs and UI issues
  • No relevant links
• This will not break child repos: it doesn't hardcode values (.e.g "kumahq" as a image registry) and it will work on Windows, system specific functions like syscall.Mkfifo have equivalent implementation on the other OS
  • It won't
• Tests (Unit test, E2E tests, manual test on universal and k8s)
  • Manually tested + all transparent proxy tests are passing
  • Don't forget ci/ labels to run additional/fewer tests
• Do you need to update UPGRADE.md?
  • There is no need
• Does it need to be backported according to the backporting policy? (this GH action will add "backport" label based on these file globs, if you want to prevent it from adding the "backport" label use no-backport-autolabel label)
  • There is no need

[michaelbeaumont]

Works for me