Update several, sometimes year old go dependencies with well-known CVEs about terratest HOT 2 OPEN

Hm ok @denis256, i get your point.

The thing is, that (at least in my case) those dependencies are downloaded whenever i run terratest.
This leads to:

• A. higher waiting times on new machines due to all the packages being downloaded
• B. Our corporate Firewall lately completely blocking us from using terratest since a nested dependency is a known malicious package.

Screenshot from the Firewall blocking downloading terratest unsing go test -v -timeout 60m -parallel 6:

from terratest.

Not sure if this is the right approach to scan for vulnerabilities since versions of transient dependencies are replaced with newer versions

For example, the mentioned golang.org/x/[email protected] in the end is replaced by golang.org/x/[email protected]
https://github.com/gruntwork-io/terratest/blob/master/go.mod#L40

from terratest.