Upload sarif for eslint results

[aeisenberg]

This change will upload the eslint results as sarif to code scanning during the CI process.

Merge / deployment checklist

• [n/a] Confirm this change is backwards compatible with existing workflows.
• [n/a] Confirm the readme has been updated if necessary.
• [n/a] Confirm the changelog has been updated if necessary.

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[aeisenberg]

It's surprising to me that code scanning is showing a bunch of alerts even though when run locally, they don't appear.

https://github.com/github/codeql-action/security/code-scanning?query=pr%3A2469+is%3Aopen

It looks like the sarif formatter is including alerts that are disabled by eslint-disable-next-line.

[rvermeulen]

Looks good to me. Once the test are passing we are good to