ci: fix trivy scan

[vincentsarago]

closes #1479

Technical Context

• Related Issues: Fixes # (issue number)
• Breaking Changes: [Yes/No] (If yes, please describe the impact and migration path)

Description

Provide a brief summary of the changes, the rationale behind them, and any specific areas you'd like the reviewers to focus on.

---

Checklist

• Linting: Code is formatted and linted (uv run pre-commit run --all-files)
• Tests: Tests pass. I have included new tests for these changes where applicable.
• Edge Cases: I have manually verified "unhappy paths" and edge cases beyond the basic success criteria (e.g., database connection timeouts, malformed input, strict mapping rejections).
• Documentation: I have updated README.md to reflect any new environment variables, configuration changes, or breaking updates.
• Accountability: I can explain the implementation logic for every line of code submitted.

---

AI tool usage

• AI (Copilot or something similar) supported my development of this PR. Use of AI tools HAVE TO be indicated.

---

Policy: We require a "human-in-the-loop." You are the author and are fully accountable for all submitted code. Please ensure all tool-generated content is thoroughly reviewed before submission to ensure it is not an "extractive contribution" that squanders maintainer time.

[github-actions]

⚠️ Performance Alert ⚠️

Possible performance regression was detected for benchmark 'TiTiler performance Benchmarks'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.30.

Benchmark suite	Current: 9c89891	Previous: 18b5835	Ratio
WebMercator response_time	0.03 s	0.02 s	1.50

This comment was automatically generated by workflow using github-action-benchmark.

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