Polishing Go companion integration

[hyangah]

• The legacy code lens had package-level and file-level tests codelenses placed around the "package" directive. Reevaluate if we want them in the Go Companion.
• Disable the vscode-go extension's code lenses when the Go Companion extension is active.
• Consider the "running test" progress status bar when triggering a test run using the code lens. After clicking the codelens, it's not very clear whether the test is running or not. (the gutter icon had changed, but it's easy to catch)
• Code coverage view: skip or correctly link files in stdlib or dependency modules.
• Document settings in the package.json so the details show up in the settings doc correctly.
• Go Companion v0.0.3 release for the coverage, and profile supports
• Release process transparency - I think the easiest is to use the github code action.

cc @firelizzard18

[firelizzard18]

The legacy code lens had package-level and file-level tests codelenses placed around the "package" directive. Reevaluate if we want them in the Go Companion.

This is doable. In the current implementation there is a one-to-one correspondence between code lens and test item. Depending on the user's configuration, a test item may not exist for a given file or package. It may be best to implement these with a "run all tests in " command where the scope is a string (really: is not a test item) to push test item resolution onto the command implementation. IIRC, I chose not to implement "run file/packages tests" because it was a non-trivial amount of work and unclear if it was needed.

Consider the "running test" progress status bar when triggering a test run using the code lens. After clicking the codelens, it's not very clear whether the test is running or not.

I'm not clear on what you mean by the "running test" progress status bar. Are you referring to a vscode-go status bar? If so, interacting with that from Go Companion would be tricky I think.

[firelizzard18]

Also:

• Improve Go Companion's test coverage