Make apiVersion and kind typing more precise

[hausdorff]

In Kubernetes resource implementations of pulumi.CustomResource, every
top-level resource type has two fields:

apiVersion?: pulumi.Input<string>
kind?: pulumi.Input<string>

These types could be more correct. For example, in the case of
apps/v1/Deployment, we might instead write:

apiVersion?: pulumi.Input<'apps/v1'>
kind?: pulumi.Input<'Deployment'>

This commit does exactly this.

Fixes #315.

[hausdorff]

The first time around on this, I missed some of the properties that are exceptions -- e.g., autoscaling/v1/CrossVersionObjectReference has both apiVersion and kind, but is not a top-level resource type, and therefore should not have the more specific typing scheme described above.

@lblackstone please do double check this to make sure I'm not missing any other exceptions to this rule... I'm leaving the second commit as a standalone for now, rather than squashing it with the previous so you can take a look.

[lblackstone]

Assuming I understand what you mean by "top-level resource type", there are a few types here that appear to be nested fields (i.e. can't create these resources directly with the API).

• DeploymentRollback
• Scale
• APIGroup
• APIResourceList
• APIVersions
• DeleteOptions
• Status
• Eviction

[hausdorff]

We've agreed to keep "%s" instead of %q for code generation.