⬆️(ci) upgrade GitHub Actions workflow steps to latest versions

[StephanMeijer]

Purpose / Proposal

I was looking into adding Docker build support for linux/arm64 in several repositories of https://github.com/suitenumerique. During that, I noticed several repositories have outdated GitHub Workflow steps. This pull request has the purpose to update them.

External contributions

• I have read and followed the contributing guidelines
• I have read and agreed to the Code of Conduct
• I have signed off my commits with git commit --signoff (DCO compliance)
• I have signed my commits with my SSH or GPG key (git commit -S)
• My commit messages follow the required format: <gitmoji>(type) title description
• I have added a changelog entry under ## [Unreleased] section (if noticeable change)
• I have added corresponding tests for new features or bug fixes (if applicable)

Testing happens when GitHub Workflows are being executed.

---

The creation of this pull request was done semi-automatically. I did automate a bunch, but I reviewed all changes manually to check if they are backwards compatible.

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: ? → npm/entities@4.5.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@4.5.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[StephanMeijer]

This PR relates to other PR's:

Project	Pull Request
suitenumerique/calc	suitenumerique/calc#15
suitenumerique/conversations	suitenumerique/conversations#297
suitenumerique/docs	suitenumerique/docs#1902
suitenumerique/e2esdk	suitenumerique/e2esdk#2
suitenumerique/find	suitenumerique/find#55
suitenumerique/projects	suitenumerique/projects#63
suitenumerique/meet	suitenumerique/meet#984
suitenumerique/meet-whisperx	suitenumerique/meet-whisperx#27
suitenumerique/meet-kyutai-moshi-stt	suitenumerique/meet-kyutai-moshi-stt#3
suitenumerique/hackdays	suitenumerique/hackdays#3
suitenumerique/people	suitenumerique/people#1072
suitenumerique/django-lasuite	suitenumerique/django-lasuite#63
suitenumerique/ui-kit	suitenumerique/ui-kit#172
suitenumerique/messages	suitenumerique/messages#555
suitenumerique/drive	#552
suitenumerique/st-deploycenter	suitenumerique/st-deploycenter#39
suitenumerique/st-home	suitenumerique/st-home#54
suitenumerique/hackdays2025	suitenumerique/hackdays2025#202

[StephanMeijer]

✅ I manually reviewed this PR and it should work just fine.

[sonarqubecloud]

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 SonarQube Cloud

[StephanMeijer]

Rebased this branch on the latest target branch and force-pushed.