Add a property mapped to `org.eclipse.jdt.core.compiler.problem.tasks` to suppress TODO diagnostics

[linghengqian]

• I expect the current extension to add a property to .vscode/settings.json that maps to org.eclipse.jdt.core.compiler.problem.tasks in settings.prefs, to suppress TODO diagnostics. I'm referring to issues like those shown in the image.
• 
• Currently, setting org.eclipse.jdt.core.compiler.problem.tasks requires developers to manually create a settings.prefs file with 505 lines, which is far too long. I'm referring to the situations mentioned in https://github.com/redhat-developer/vscode-java/wiki/Settings-Global-Preferences and Unable to suppress TODO diagnostics using java.errors.reportTodoComments or java.errors.suppressedDiagnostics #4196 .
• I'm not sure if I've missed any known enhancement issues, such as whether there's an issue that mentions grouping known issues to suppress different groups of issues, like in IntelliJ IDEA?

[fbricon]

you can create a settings.prefs with a single org.eclipse.jdt.core.compiler.problem.tasks=ignore line

[linghengqian]

you can create a settings.prefs with a single org.eclipse.jdt.core.compiler.problem.tasks=ignore line

Wow, I just realized that writing only one line in .vscode/java.prefs works too. Should I close this issue? It seems that unless #3059 is merged, there's no way to further improve this configuration.

[fbricon]

3509 is about formatting configuration. We don't plan on adding 200+ new vscode config keys to match the existing config from jdt .prefs file. So I think it's ok to close this.