Run ESLint on PR fork without generating report

[pierlon]

Summary

• Skips ESLint report generation step when PR is opened from a repo fork
• Adds ESLint step specifically for PRs opened from a repo fork

[github-actions]

Plugin builds for 824b36d are ready 🛎️!

• Download development build
• Download production build

[westonruter]

This will prevent the following from happening as in #5871:

Correct?

Why again is it that without this change, the step is skipped?

I believe I'll also need to remove this from the required checks for the tests to pass:

[pierlon]

This will prevent the following from happening as in #5871... Correct?

It should not have been showing in the first place since the action that creates the check did not run at all.

I believe I'll also need to remove this from the required checks for the tests to pass

I wonder if that's the reason why the check appears even when the ataylorme/eslint-annotate-action did not run to create it... Yes you could remove that as a required check since it will never be marked as complete on PRs from forks.

Why again is it that without this change, the step is skipped?

I suppose you mean the "Annotate code linting results" step. That was set to skip in #5656.

[westonruter]

Ah, npm run lint:js:report also does the linting, so that is why this is is limited to forks.