Add golang env setup to node e2e

[ehashman]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Without it, node e2e tests fail to run for me locally:

ehashman@red-dot:~/src/k8s$ make test-e2e-node FOCUS="\[NodeConformance\]|\[NodeAlphaFeature:.+\]" SKIP="\[Flaky\]|\[Serial\]" TEST_ARGS='--feature-gates=AllAlpha=true,CSIMigration=false,RotateKubeletServerCertificate=false'
+++ [0305 15:57:59] Building go targets for linux/amd64:
    vendor/github.com/onsi/ginkgo/ginkgo
Creating artifacts directory at /tmp/_artifacts/210305T155809
Test artifacts will be written to /tmp/_artifacts/210305T155809
No need to refresh sudo credentials
test/e2e_node/runner/local/run_local.go:31:2: cannot find package "k8s.io/klog/v2" in any of:
	/home/ehashman/.local/go-1.16/src/k8s.io/klog/v2 (from $GOROOT)
	/home/ehashman/go/src/k8s.io/klog/v2 (from $GOPATH)
test/e2e_node/runner/local/run_local.go:27:2: cannot find package "k8s.io/kubernetes/test/e2e_node/builder" in any of:
	/home/ehashman/.local/go-1.16/src/k8s.io/kubernetes/test/e2e_node/builder (from $GOROOT)
	/home/ehashman/go/src/k8s.io/kubernetes/test/e2e_node/builder (from $GOPATH)
test/e2e_node/runner/local/run_local.go:28:2: cannot find package "k8s.io/kubernetes/test/e2e_node/system" in any of:
	/home/ehashman/.local/go-1.16/src/k8s.io/kubernetes/test/e2e_node/system (from $GOROOT)
	/home/ehashman/go/src/k8s.io/kubernetes/test/e2e_node/system (from $GOPATH)
test/e2e_node/runner/local/run_local.go:29:2: cannot find package "k8s.io/kubernetes/test/utils" in any of:
	/home/ehashman/.local/go-1.16/src/k8s.io/kubernetes/test/utils (from $GOROOT)
	/home/ehashman/go/src/k8s.io/kubernetes/test/utils (from $GOPATH)
make: *** [Makefile:270: test-e2e-node] Error 1

Technically I'm maybe supposed to use kubetest? idk?

Which issue(s) this PR fixes:

This patch fixes the above issue. Not sure if this is the best way to do this but it works!

Special notes for your reviewer:

n/a

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

/cc @BenTheElder
/sig node testing

[ehashman]

/priority backlog

[BenTheElder]

/lgtm
/approve

[BenTheElder]

/triage accepted

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BenTheElder, ehashman

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• hack/OWNERS [BenTheElder]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ehashman]

/retest
flakes...

[BenTheElder]

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/99874/pull-kubernetes-unit/1367990215217516544
=> filed #99877 (doesn't appear to have an existing issue)

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/99874/pull-kubernetes-node-e2e/1367990215259459584/
=> #98649

(cross linking the existing one as well for visibility on occurrences).

[bobbypage]

/lgtm

nice. You can also invoke test/e2e_node/runner/remote/run_remote.go manually to more closely mirror the tests on prow like noted in #99805 (comment)

I had same issues as you noted, had to set GO111MODULE=on to run it manually (from within GOPATH)