chore: regenerate fixture results for Trivy DB update

[andrzej-janczak]

Trivy vulnerability DB updated since last fixture generation. Regenerated all results.xml files using the scripts/regenerate_fixtures.py script against the latest codacy-trivy:latest local Docker image (Trivy 0.70.0).

Changed fixture counts vs previous:

• all-patterns: minor updates
• pattern-vulnerability-critical: minor updates
• pattern-vulnerability-high: 57 → 49 issues
• pattern-vulnerability-medium: 75 → 89 issues
• pattern-vulnerability-minor: 19 → 21 issues

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request updates various vulnerability test result XML files under docs/multiple-tests/. The modifications refine vulnerability descriptions to be more detailed and standard, consolidate or remove redundant golang/stdlib entries, and introduce new vulnerability entries for npm/axios and golang/stdlib. As there are no review comments, I have no feedback to provide.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

The pull request successfully updates the test fixture results to reflect changes in the Trivy vulnerability database. The Codacy analysis indicates that the changes are up to standards, and no new issues or security concerns were identified by the review agents.

The updated results align with the expected issue counts (High: 49, Medium: 89, Minor: 21) and correctly include full vulnerability descriptions and fix availability information. No logic gaps or implementation failures were found.

Test suggestions

• Verify that all results.xml files are valid XML and follow the Checkstyle format required by the parser.
• Confirm that the number of <error> entries in the severity-specific results files (e.g., pattern-vulnerability-high) matches the updated totals in the PR description.
• Validate that the message attributes in the XML correctly incorporate the new CVE descriptions and 'no fix available' or 'update to X' suffixes.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}