Skip waitDaemonset in E2E mode to prevent race condition

In E2E test mode, the bash script's waitDaemonset() could exit with
error after 10 minutes while the Go test's isDaemonsetReady() was
still polling. This created a race where:

1. Go test calls StartCommand() which runs bash script async
2. Bash script calls waitDaemonset() and waits 10 mins
3. Go test calls isDaemonsetReady() and waits 10 mins
4. If bash times out first, it calls exit 1, killing the process
5. Go test is left polling a dead command

Solution: When isE2E=true, skip the bash-level wait since the Go
test framework handles pod readiness checking via isDaemonsetReady().

For manual CLI usage (isE2E=false), the wait still runs as before
to provide user feedback.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: memodi

scripts/functions.sh

@@ -779,6 +779,12 @@ function defaultValue() {
 }
 
 function waitDaemonset(){
+    # In E2E test mode, skip waiting here as Go tests handle it via isDaemonsetReady()
+    if [[ "$isE2E" = true ]]; then
+      echo "E2E mode: Skipping daemonset wait (handled by test framework)"
+      return 0
+    fi
+
     echo "Waiting for daemonset pods to be ready..."
     # Increase timeout for CI environments where image pulls can be slow
     # 60 retries × 10 seconds = 10 minutes total