Analyze should support a baseline for existing violations (warnings and failures)

[DirkMahler]

If rules are added to an existing code base then there are usually lots of violations (warnings or failures) that cannot be fixed immediately. A common strategy is to ignore them first and fix them step by step (e.g. as part of a feature). Currently we rely on tools like Teamscale or SonarQube for managing such issues ("tolerate"), but for the latter this is no longer supported for issues created by external tools like jQA.

Therefore it would be helpful if a baseline of existing violations could be stored along the project's source code in the version control system (similar to ArchUnit's freeze mechanism):

• Every violation in that file (identified by the already existing key for violations) will be automatically suppressed
• any fixed violation will automatically be removed from the baseline file and can be checked in by a developer as updated baseline