Stop creating linter report files in CI

[SpecLad]

Motivation and context

Currently, when one of the linters reports a problem, if you want to see what that problem is, you have to do the following:

1. Click on the "Details" link in the PR.
2. Click "Summary".
3. Click the artifact (also, depending on the browser, choose where to save it).
4. Open the downloaded file (which is an archive).
5. Open the report file from the archive.
6. Delete the archive after you're done.

That is far too much hassle, and all it gives you is a slightly fancier- looking report (and sometimes not even that, like in the case of black).

So just remove all the report building and uploading. Now the above procedure is reduced to:

1. Click "Details".
2. Expand the appropriate build step.

How has this been tested?

I deliberately introduced errors specific to each linter and used act to make sure the workflows run as expected.

Checklist

• I submit my changes into the develop branch
• [ ] I have added a description of my changes into the CHANGELOG file
• [ ] I have updated the documentation accordingly
• [ ] I have added tests to cover my changes
• [ ] I have linked related issues (see GitHub docs)
• [ ] I have increased versions of npm packages if it is necessary
  (cvat-canvas,
  cvat-core,
  cvat-data and
  cvat-ui)

License

• I submit my code changes under the same MIT License that covers the project.
  Feel free to contact the maintainers if that's a concern.

[sizov-kirill]

Looks great, I'm tired of downloading this linter's artifacts too