🛡️ Sentinel: [CRITICAL] Fix hardcoded secret for XML-RPC bypass

[Snider]

🚨 Severity: CRITICAL
💡 Vulnerability: A hardcoded token (xrpc-9f8e7d6c5b4a) was present in the Nginx configuration, acting as an authorization bypass for the WordPress xmlrpc.php endpoint.
🎯 Impact: If an attacker discovered the token, they could bypass the intended block on the XML-RPC endpoint, potentially exposing the application to brute-force attacks, DDoS amplification (pingback attacks), and other known XML-RPC vulnerabilities.
🔧 Fix: Replaced the conditional $arg_token logic with an unconditional deny all; directive. Also disabled access and not_found logging to prevent log flooding.
✅ Verification:

1. Check the server-php/config/conf.d/wordpress.conf to ensure location = /xmlrpc.php contains only deny all;, access_log off;, and log_not_found off;.
2. A syntax check was successfully executed using nginx -t with a test configuration wrapper.

---

PR created automatically by Jules for task 9324265487148187022 started by @Snider

[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.