chore: Update outdated GitHub Actions versions

[pgoslatara]

Description

This PR updates outdated GitHub Action versions.

Motivation and Context

Move this repo to use up to date Action versions to benefit from newer features, security fixes and so any future deprecations are less likely to impact the repo.

How Has This Been Tested?

The CI pipeline will test the majority of these changes.

Types of changes

• Updated actions/checkout from v4 to v6 in .github/workflows/push.yaml
• Updated actions/checkout from v4 to v6 in .github/workflows/analyze-project.yaml
• Updated actions/download-artifact from v4 to v7 in .github/workflows/push.yaml
• Updated actions/checkout from v4 to v6 in .github/workflows/build-project.yaml
• Updated actions/checkout from v4 to v6 in .github/workflows/pr-pull.yaml
• Updated actions/checkout from v4 to v6 in .github/workflows/check-format.yaml
• Updated actions/upload-artifact from v4 to v6 in .github/workflows/push.yaml
• Updated actions/upload-artifact from v4 to v6 in .github/workflows/sign-windows.yaml
• Updated actions/upload-artifact from v4 to v6 in .github/workflows/build-project.yaml
• Updated actions/download-artifact from v4 to v7 in .github/workflows/sign-windows.yaml
• Updated actions/checkout from v4 to v6 in .github/workflows/scheduled.yaml
• Updated actions/download-artifact from v4 to v7 in .github/workflows/dispatch.yaml
• Updated actions/checkout from v4 to v6 in .github/workflows/sign-windows.yaml
• Updated actions/checkout from v4 to v6 in .github/workflows/publish.yaml
• Updated actions/checkout from v4 to v6 in .github/workflows/dispatch.yaml

Checklist:

• My code has been run through clang-format.
• I have read the contributing document.
• My code is not on the master branch.
• The code has been tested.
• All commit messages are properly formatted and commits squashed where appropriate.
• I have included updates to all appropriate documentation.

[WizardCM]

Please fill in the PR template and read the contributing guidelines.

[PatTheMav]

It is permitted to tick elements of the checklist that clearly don't apply (e.g. clang-format doesn't apply to YAML files, so the PR "implicitly" passes that requirement).

I still expect that a full CI test was done on your fork (by checking pull request pushes, pushes to master branch, scheduled and dispatched workflow runs, pushed a tag and released a version, etc.) to be able to tick that checkbox.

Would also be great to hear if the changes in each action have been checked for any potential breaking changes or impacts to our release process.

---

Also please use CI as the commit prefix (it's a convention of the project and is not explicitly mentioned in our contribution guidelines, another thing I'm working on to update).