Define a mapping between REST resource name and kind/apiVersion

Allows clients to abstractly map user input to generic resource
paths as per docs/api-conventions.md

Extracted from #2000 and supports #1958
I am concerned that such "helpful" behavior is going to cause weird stuff like clients asking for most resources in v1beta2 except for minions, which get downgraded to v1beta1 because they're using the wrong term. This could lead to really hard to figure out bugs when some of your objects don't really have all of their fields set because they were transported in a version that you didn't expect.