[WIP] Adds integration test framework and initial tests for GCP cloud controller manager

[seans3]

• Adds integration tests for GCP cloud-controller-manager
• (within integration test directory):

$ go test -v ./...
...
--- PASS: Test_CloudControllerManagerGCP (12.28s)
PASS
...

NOTE: There is currently a goroutine leak caused by the NodeIPAMController loop

	found unexpected goroutines:
	[Goroutine 4414 in state chan receive, with k8s.io/apimachinery/pkg/watch.(*Broadcaster).loop on top of the stack:
	k8s.io/apimachinery/pkg/watch.(*Broadcaster).loop(0xc008df8500)
		/home/sean/go/pkg/mod/k8s.io/apimachinery@v0.31.0/pkg/watch/mux.go:268 +0x66
	created by k8s.io/apimachinery/pkg/watch.NewLongQueueBroadcaster in goroutine 4347
		/home/sean/go/pkg/mod/k8s.io/apimachinery@v0.31.0/pkg/watch/mux.go:93 +0x125
...

NOTE2: There is currently no BUILD file to run the test using bazel -- yet.

[k8s-ci-robot]

This issue is currently awaiting triage.

If the repository mantainers determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: seans3
Once this PR has been reviewed and has the lgtm label, please assign jprzychodzen for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[seans3]

/retest

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale