security fixes go part

[ivolzhevbt]

continuation of #963

this part switches to go modules and fixes

vulnerability	severity	description
G304	MEDIUM	While input is not controlled by user input it's an equal effort to sanitize input or suppress warning I went with sanitizing input
G703	MEDIUM	The warning is about uncatched error from deferring closing a file. While nothing can be done if this will error, it's clearer to explicitly ignore it

Thank you for the maintaining vscode-kubernetes-tools and please let me know what do you think about it?

[bacongobbler]

While I understand the reasoning behind the change, this is the standard convention, and it performs exactly the same as your proposed change. This convention is described in the Effective Go guide, which is referred to when styling conventions are called into question.

This document gives tips for writing clear, idiomatic Go code. It augments the language specification, the Tour of Go, and How to Write Go Code, all of which you should read first.

I would suggest that Salus should be updated to follow the standard convention.

[ivolzhevbt]

@bacongobbler thanks for your feedback
Salus uses gosec under the hood, and I'm quite sure they might be not very cooperative regarding this rule.
at least their recommendation securego/gosec#512 here proposes to explicitly handle errors.

will silencing this particular warning be considered?

[itowlson]

Talked to @bacongobbler and he's happy with the revised PR so will merge - thanks!