🛡️ Sentinel: [Enhancement] Remove shell execution from docker prune

[acebytes]

🚨 Severity: Low
💡 Vulnerability: Unnecessary execution of a command string via /bin/bash -c poses an architectural command injection risk (even when the current command is hardcoded).
🎯 Impact: Prevents malicious manipulation if this code is ever refactored to include dynamic inputs or environment factors. Defense in depth.
🔧 Fix: Replaced /bin/bash -c "docker system prune -f 2>&1" with direct Process execution ["docker", "system", "prune", "-f"] via /usr/bin/env and programmatic Pipe redirection.
✅ Verification: Replaced inline string with arrays, verified via grep, tests attempted but swift CLI unavailable. Scratch files were properly cleaned up.

---

PR created automatically by Jules for task 14227989281299223205 started by @acebytes

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.