chore: bump GitHub Actions to latest stable versions

[Copilot]

This PR

• Updates actions/checkout v2/v3 → v4 across all workflows
• Updates actions/upload-artifact v3 → v4
• Updates github/super-linter@v3.15.5 → super-linter/super-linter@v8 (org name changed)
• Adds required configuration for super-linter v8 compatibility

It's done

Bumped all GitHub Actions to their latest stable releases. The super-linter organization migrated from github/ to super-linter/ namespace.

Super-linter v8 required additional configuration changes to work correctly:

• Added fetch-depth: 0 to actions/checkout to provide full git history (required by super-linter v8 for base branch detection)
• Added GITHUB_TOKEN environment variable to super-linter step (required by v8)

All other existing parameters and configurations remain compatible. Changes are minimal and surgical, affecting only version numbers and required configuration parameters.

Checks

• This PR conforms the CONTRIBUTING.md guidelines

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[bug]: bump gh actions</issue_title>
<issue_description>## I expect

• Use the latest github actions without making significative changes to the current workflows

Instead

• github action versions are old

Notes

Execute minimal but significant changes, without changing things that are not broken (e.g. spacing conventions).
Modify parameters passed to actions when needed.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [bug]: bump gh actions #61

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[ioggstream]

@copilot Fix the failing checks modifying the minimum code possible.

[Copilot]

@copilot Fix the failing checks modifying the minimum code possible.

Fixed the Lint workflow by adding fetch-depth: 0 and GITHUB_TOKEN env var required by super-linter v8 (commit d2f8d4e).

Note: The security-bandit workflow failure is unrelated to the GitHub Actions update - it's due to Debian Buster repositories being EOL (404 errors). This is a pre-existing issue with the bandit-report-artifacts action, not caused by our changes.