fix: improve Redis detection logic

[javiercasares]

Summary

• reuse the active Redis client exposed by WordPress object cache implementations when available
• fall back to a temporary Redis connection configured via the WP_REDIS_* constants and close it after use
• keep the CLI detection fallback while preventing Redis-related exceptions from bubbling up

Testing

• vendor/bin/phpstan analyse --memory-limit=1G wpvulnerability-general.php
• vendor/bin/phpunit (fails: missing /tmp/wordpress-tests-lib)
• vendor/bin/phpcs (fails: missing PHPCompatibilityWP sniff)

---

https://chatgpt.com/codex/tasks/task_b_69045749c8d48321ac11ed4d420ae004

[amplify-security]

🔍 Amplify code check status:  

⚠️ 0 issues detected in   📄 1 file and   ❇️ 126 lines of code   🛠️ using Opengrep

Last updated by commit d1fea33 at 2025-10-31 06:53:43 UTC.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud