fix: remove shell=True in cmd_git to prevent command injection (issue #5272)

[chrislazar25]

Summary: Fix command injection vulnerability in /git by removing shell=True and using list-based subprocess invocation.

Technical Details:

• Root Cause: cmd_git() constructs "git " + args and passes it to subprocess.run(..., shell=True). User input is concatenated directly into a shell command string, allowing injection via shell metacharacters (;, |, `, etc.).
• Mechanism: The old code allowed /git status; cat ~/.ssh/id_rsa to execute the injected command after git ran. The fix switches to a list-based call (["git"] + shlex.split(args) with shell=False), so shell metacharacters become literal git arguments that git rejects as unknown commands.

Verification:

• Confirmed adherence to CONTRIBUTING.md. Ran python -m pytest tests/. 455 passed, 1 pre-existing env failure (test_voice requires audio hardware). Pre-commit hooks (isort, black, flake8, codespell) all green.
• Tested manually end-to-end:
  • git status → exit 0, correct output ✅
  • git log --oneline -1 → exit 0, correct output ✅
  • git status; echo INJECTED_YES (old code): INJECTED_YES appeared in output — exploitable
  • git status; echo INJECTED_YES (new code): exit 1, git: 'status;' is not a git command — blocked ✅

Blast Radius:

• Impact: Low. Shell metacharacters in /git commands that previously worked as shell syntax will now fail. These were security bugs, not intended features.
• Trade-offs: Single-character change, no performance impact. shlex.split() handles quoted arguments correctly (more robust than a naive .split()).

---

Fixes #5272