Pluggable lint/format engine

[mshr-h]

Maybe we can do something like this?

"verilog.linter": "IcarusLinter",
"verilog.linter.icarusLinter.command": "/usr/bin/iverilog -t null -Wall $FILEURI",
"verilog.linter.icarusLinter.file_patterns": ["*.v", "*.sv"],
"verilog.linter.icarusLinter.pattern: "^[^:]\+:\(\d\+\): \(warning\|error\|syntax error\)\(: \(.\+\)\)\?",
"verilog.linter.icarusLinter.pattern_order: ["line": 1, "type": 2", "message": 4],
"verilog.linter.icarusLinter.pattern_type: ["error": ["error", "syntax error"], "warning": ["warning"]],
"verilog.formatter": "verilogFormat",
"verilog.linter.verilogFormat.command": "verilogFormat -f $FILEURI",
"verilog.linter.verilogFormat.useTempFile": true,

[Raamakrishnan]

This might be the better way to handle all the possible lint tools that can be. But these settings also feel like we are re-inventing VSCode tasks/task provider and problem matcher

The problem matchers are the most reusable thing across users. But the file extensions, command line path and args vary vastly.

Can we go complete "hands-off" by providing just the problem matcher, and let the users write their own tasks? Or we can have some sort of a basic task format like a template. I may have to see if task provider can be used to give this template