CI: Update GitHub actions

[RytoEX]

Description

Update all GitHub actions where updates were available.

Important

Because this updates .github/workflows/sign-windows.yaml, the commit hash for consuming that must be updated, which means this requires a merge commit.

Motivation and Context

Want to update actions and reduce or eliminate CI warnings about deprecations.

How Has This Been Tested?

It hasn't yet. First-party GitHub Actions were already updated on obs-deps and seem to be working fine. However, we use far more actions on obs-studio.

Types of changes

• Bug fix (non-breaking change which fixes an issue)

• Code cleanup (non-breaking change which makes code smaller or more readable)

• CI

Checklist:

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

[PatTheMav]

I take it the actions that don't have a version tag comment behind their commit hash have no versioning scheme for their action (or the last version is very far behind the commit)?

[RytoEX]

I take it the actions that don't have a version tag comment behind their commit hash have no versioning scheme for their action (or the last version is very far behind the commit)?

Correct, except for the steam actions, where I forgot to add the version tag comments. I will add those in a rebase/push.

Homebrew/actions does not use releases/tags.
obsproject/obs-crowdin-sync does not use release/tags.

korelstar/xmllint-problem-matcher does have releases/tags, but the updated commit is not part of one. Here is the diff between v1.2.0 and the commit I picked: korelstar/xmllint-problem-matcher@1bd292d...b105cfa