Suggestion: Ignore compiler warnings and information from specified directories

As a user of the vscode-java extension, I would like to ignore Java compiler warnings and information coming from certain directories.

Generated code and unit tests often generate warnings from the compiler. I would like to have warnings coming from certain directories suppressed so it'll be easier to find warnings from code we're interested in.

files.ignore is not good enough because sometimes you want to ignore warnings coming from unit tests. For example, you might want to test your equals() method against different objects, but you will get an information message telling you that it's an unlikely argument.

For now, entering src/main/** into the problems filter seems to be good enough for now, but I would like to create a workspace with some sane defaults for my coworkers to use when pulling the project.

Beginne damit, den bestehenden Problems-Filter und das Verhalten von files.ignore in der vscode-java-Erweiterung zu untersuchen, und verfolge anschließend, wie Compiler-Warnungen und -Informationen angezeigt werden. Die Aufgabe ist erfüllt, wenn ein Workspace Verzeichnisse angeben kann, deren Compilerdiagnosen unterdrückt werden, ohne diese Dateien von anderem Projektverhalten auszuschließen.