Explore ways to sync the right version of the go-langserver

[ramya-rao-a]

See #706 (comment)

Or gopkg.in

[ramya-rao-a]

• Updating language server as part of post-install of the extension:

We support the language server binary being in user's GOPATH (which can be different from the default or the one set as env var), PATH or a whole another location (using go.toolsGopath).

Therefore, adding a post install step (which wouldnt be aware of user settings) for syncing the language server is a non-started

• Language server uses tagging and the extension uses gopkg.in to get the minimun supported version

Only catch is that after a couple of major versions, user's workspace can get crowded with all the multiple versions of golanguage server

[ramya-rao-a]

In the next update of the Go extension, the user will be prompted when we attempt to use features from the language server that are not yet supported in the version that the user has.

We do this by looking at the capabilities returned by the server.

This should be more than enough to let the user know to update their version of the language server.

Experimental features can be controlled by the go.languageServerExperimentalFeatures setting and using the middleware to not use the results from the language server if needed.

Therefore, closing this issue.