update kind to v0.6.0 and move ec2-meta-data-proxy to test root

[bwagner5]

Issue #, if available:
N/A

Description of changes:

• Updated KinD to v0.6.0
• Moved the test metadata into test root so that it can be used across future tests

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[jaypipes]

Let's steer clear of Go submodules in the repo. multi-module repos are an extreme pain in the you-know-what. I've learned this from painful experience recently:

https://github.com/golang/go/wiki/Modules#should-i-have-multiple-modules-in-a-single-repository
golang/go#35878

In short, if we used multiple Go modules in a single repo, we'd need to remember to apply a semver "prefixed" Git tag every time we issued a release, one for each Go submodule. It's a recipe for disaster and we can do just fine with a single semver Git-tagged repo with a single root Go.mod.

[jaypipes]

You know, the more I think about it, the more I think this PR is a perfect opportunity to rename the binary here to make it 100% clear it's simply a test helper/fake and not something that should or would be deployed to a production setup.

How about we rename cmd/ec2-meta-data-proxy to cmd/test-ec2-metadata-fake or cmd/ec2-metadata-test-proxy or cmd/ec2-metadata-test-helper (your choice)?

Thoughts?
-jay

[bwagner5]

yeah that's not a bad idea, I think I like ec2-metadata-test-proxy, I'll update

[jaypipes]

Thanks for making that name change, Brandon!