chore(deps): update github actions

[alma-renovate-bot]

This PR contains the following updates:

Package	Type	Update	Change
codex-/return-dispatch	action	major	v1 -> v2
ubuntu	github-runner	major	22.04 -> 24.04

---

Release Notes

codex-/return-dispatch (codex-/return-dispatch)

v2

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[Benjamin-Freoua-Alma]

Need @alma/squad-devx validation 🙏

[github-actions]

⏳E2E tests are currently running.
➡️ You can follow their progression here.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[carine-bonnafous]

@remi-zuffinetti if I understand correctly, python was included in ubuntu-22.04 but is no more in ubuntu-24.04 ?

[remi-zuffinetti]

@remi-zuffinetti if I understand correctly, python was included in ubuntu-22.04 but is no more in ubuntu-24.04 ?

Not, it is still, but it is now packaged in a way that prevent directly running pip install at the system level, so that there is no conflict between packages managed by apt, and packages managed by pip.
There are plenty of way to manage that issue (create a virtualenv first, install as a user, etc..) but I preferred to rely on just using our custom installation of Python with this action, so that it's simple, and we have control over the version we used, instead of relying on updates to the runner image.
But that's a personal taste, I can take other opinions

[github-actions]

❌ E2E tests have failed.
➡️ You can find the results here.