Add problem matchers

[mhucka]

GitHub Problem Matchers are a mechanism that enable workflow steps to scan the outputs of GitHub Actions for regex patterns and automatically write annotations in the workflow summary page. Using Problem Matchers allows information to be displayed more prominently in the GitHub user interface.

This add problem matchers for Pylint, Pytest, MyPy, and Black output. More problem matchers can be added in the future as more checks are added to the CI workflows.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.13%. Comparing base (0551f85) to head (0c0d866).
Report is 18 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7122   +/-   ##
=======================================
  Coverage   98.13%   98.13%           
=======================================
  Files        1093     1093           
  Lines       95528    95528           
=======================================
  Hits        93745    93745           
  Misses       1783     1783           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[pavoljuhas]

Can you please add a temporary commit that would introduce all errors handled here?

It will verify if matchers work and show what is their output like.

[mhucka]

Can you please add a temporary commit that would introduce all errors handled here?

It will verify if matchers work and show what is their output like.

Just so I'm clear, you mean, make a commit as part of this PR, to make changes that will trigger the problem matchers?

It's a great idea to have test cases. I wonder if we could actually add test files somewhere in a directory and leave them there, then (after verifying the beahvior) configure the CI checks to ignore the directory?

If so, what would be a good location for those test files?