fix: Update style-check workflow to use latest version from upstream

[AaronDewes]

This improves the security of the workflow. Alternative to #258.

[AaronDewes]

@billyvg Just FYI: For this fix to be effective, it needs to be cherry-picked to every branch of this repository that contains the vulnerable workflow.

Alternatively, you can also delete the stale branches.

I think there is also an option that allows disabling any workflow named .github/workflows/style-check.yml through the GitHub settings (So you can simply rename the patched version on the main branch and don't have to interact with any other branches), but I'm not fully sure how this works.

[sentry]

Bug: The ataylorme/eslint-annotate-action is passed an incorrect repo-token parameter. The action expects GITHUB_TOKEN, which will cause authentication to fail.
_{Severity: HIGH | Confidence: High}

🔍 Detailed Analysis

The ataylorme/eslint-annotate-action is configured to receive an authentication token via the repo-token parameter. However, an analysis of the action's definition, for both the previous and updated versions, confirms that it expects this token to be passed using the GITHUB_TOKEN parameter. Because the wrong parameter name is used, the action will not receive the necessary authentication token. This will cause the step to fail, preventing ESLint annotations from being posted to pull requests.

💡 Suggested Fix

In the .github/workflows/style-check.yml file, change the parameter name from repo-token back to GITHUB_TOKEN for the ataylorme/eslint-annotate-action step to ensure the authentication token is passed correctly.

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: .github/workflows/style-check.yml#L56

Potential issue: The `ataylorme/eslint-annotate-action` is configured to receive an
authentication token via the `repo-token` parameter. However, an analysis of the
action's definition, for both the previous and updated versions, confirms that it
expects this token to be passed using the `GITHUB_TOKEN` parameter. Because the wrong
parameter name is used, the action will not receive the necessary authentication token.
This will cause the step to fail, preventing ESLint annotations from being posted to
pull requests.

_{Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 7729258}

[AaronDewes]

According to the docs, this is wrong: https://github.com/ataylorme/eslint-annotate-action/tree/v2?tab=readme-ov-file#inputs