update github workflows to use latest version of checkout and setup-python

[sjha2048]

Checklist

closes #1967

• No CHANGELOG update needed

• No new tests needed

• No documentation update needed

[mr-tz]

great thank you! what about this release https://github.com/actions/checkout/releases/tag/v4.1.1?

could you also update the setup-python action, see the annotations/warnings, e.g. here: https://github.com/mandiant/capa/actions/runs/8001733292

[sjha2048]

hi @mr-tz, any particular reason for using commit hashes instead of version numbers?

could you also update the setup-python action

sure.

[mr-tz]

Thanks, see https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions

Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. When selecting a SHA, you should verify it is from the action's repository and not a repository fork.

[sjha2048]

TIL!
Thanks, will update shortly.

[mr-tz]

Thanks, there's still a few to fix in the build and CI workflows. Let me know if you want to fix them as well or if we should track them separately.

[sjha2048]

works for me either way, can you help me in listing them?
I'll also go though the logs, if there are too many changes then I'll raise separate PRs

[mr-tz]

[sjha2048]

@mr-tz I have updated these actions.

[mr-tz]

Awesome, thank you!