Properly test linter configs
Currently the linter configs are only tested rudimentarily. We should enhance testing, meaning:
- the test files should include as much violating code as possible
- the output files must be updated accordingly
The idea is, that the test files violate ALL linter errors. If we can do that, we can schedule recurring pipeline runs, so that we test the linter each night.