Register additional problem matchers for error output

[mcr-pon]

While running CI, we're encouraging developers to generate a linting report. There's an easy hack to use that report to generate 'compact' output. And setup-node has a 'problem matcher' to translate those errors into annotations, visible in your PR files changed tab.

However, the aforementioned hack to generate compact output from the report, generates it with a minor difference (the rule at the end of the line is enclosed by [] instead of (). We could use our own combined CI action to add a modified problem matcher to catch these too.

[mcr-pon]

Official docs: https://github.com/actions/toolkit/blob/main/docs/problem-matchers.md