[RFC]: Improve JS lint issue content to include only failing cases

[Planeshifter]

This issue proposes to rework the GitHub actions job that creates JS lint issues to only include the failing test cases and not extra information such as "Linting file: ..."

Could either use regular expression stripping of non-relevant text or generate structured ESLint output (see available formatters) and extract it from there. This is complicated by fact that we want to extract only the errors and not display any warnings.

We could probably use the eslint-formatter-unix for this, too.

Example issue: stdlib-js/stdlib#5454

Time with AI: 1h
Time without AI: 2h

[Ponraaj]

@Planeshifter I came across the --quite flag in eslint to ignore all the warnings (reporting only the errors). Can I try using it to fix this problem?

I'm planning to add the flag here

[kgryte]

@Ponraaj that is not what we want. Also, this repository contains issues which already have assignees and are part of a separate effort. I suggest consulting the main project issue tracker for other tasks to pick up.

[Planeshifter]

PR-URL: stdlib-js/stdlib#5751

Loom recording: https://www.loom.com/share/70d6c096b70b4df4a16fa48d80729fce?sid=04aa1988-c81f-4298-aef8-4e94b3962604

Time to completion: 1h 2min.

[Planeshifter]

Notes: I had to think about how to approach this for a bit and ended up discarding various ideas. I believe I would have been significantly faster with AI since I encountered a bunch of errors when updating the make rule that could have been avoided.