ci: update lock and ci

[vincentsarago]

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
• 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. See our policy about AI tool use. Use of AI tools must 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.