chore(docker): refresh bundled proxy toolchain image

[github-actions]

🤖 Automated bundled-toolchain refresh

The prebuilt Caddy/CrowdSec toolchain image was rebuilt (daily
--no-cache --pull, or a tracked-pin change) and produced a new
digest.

	Tag	Digest
Old	caddy-crowdsec-38bb7bfc92d170ec	sha256:d941a9cee536f3b163798ce951609217ec083ff72be2ec2b67a4d9ff89db1960
New	caddy-crowdsec-e2f486a3317fa499	sha256:e355fe07ef48ff18f609079e7b1bf81930baa74b095af20435157b9d926d4cbe

The Trivy CRITICAL/HIGH gate on the new image passed on the rebuild
run. Merging updates the shipped Caddy/CrowdSec binaries.

Verification

• CI green (verify-toolchain-pin, Docker Build, integration)
• Trivy diff on the final app image shows no new CRITICAL/HIGH

Auto-generated by .github/workflows/toolchain-image.yml.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[github-actions]

✅ Supply Chain Verification Results

✅ PASSED

📦 SBOM Summary

• Components: 1870

🔍 Vulnerability Scan

Severity	Count
🔴 Critical	0
🟠 High	0
🟡 Medium	0
🟢 Low	0
Total	0

📎 Artifacts

• SBOM (CycloneDX JSON) and Grype results available in workflow artifacts

---

_{Generated by Supply Chain Verification workflow • View Details}