Add bilingual security/robustness analysis for PR #3489 (@inspectFile)

[Easton97-Jens]

Motivation

• Provide a focused, evidence-based security and robustness analysis of PR Hardening: Avoid shell-based popen usage in InspectFile operator owasp-modsecurity/ModSecurity#3489 which replaces shell-based popen() in @inspectFile with fork()/execv() and related process handling.
• Deliver a reproducible artifact (report + diffs + metadata) that documents findings, hypotheses, and a concrete test/reproduction plan for maintainers and reviewers.

Description

• Add a bilingual (German / English) Markdown report modsecurity_security_analysis.md that contains: executive summary, confirmed findings, probable risks, hypotheses, PR analysis, relevant code paths, test plan, recommendations, and final verdict.
• Save the PR artifacts used for the analysis as analysis_artifacts/pr3489.patch, analysis_artifacts/pr3489_inspect_file_final.patch, and analysis_artifacts/pr3489_metadata.json to allow reviewers to reproduce the static diff inspection.
• The report and artifacts are based on static inspection of src/operators/inspect_file.cc, src/operators/inspect_file.h, rule/operator call sites, and the PR metadata for Hardening: Avoid shell-based popen usage in InspectFile operator owasp-modsecurity/ModSecurity#3489; the report explicitly marks runtime claims as unverified where applicable.

Testing

• Performed static verification and artifact retrieval commands (rg, sed, curl to GitHub API/patch-diff, nl to view files) which all completed successfully and produced the inputs used for the analysis.
• No runtime or integration tests were executed against the modified C++ code in this change; the report contains a concrete, reproducible test plan to validate behavior under multithreaded/high-load conditions.

---

Codex Task