TPUVirtualMachine: CRD/Mapper/Fuzzer

[justinsb]

• TPUVirtualMachine: generated scripts
• autogen: apis/tpu/v1alpha1/generate.sh
• TPUVirtualMachine: Update types from generated
• TPUVirtualMachine: Create fuzz test
• proto: add our own bindings for tpu.v2

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from justinsb. 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

[justinsb]

Two points of interest:

• The CRD naming is unusual. The proto "Node" resource in V1 is very different from the "Node" resource in V2. I went with TPUVirtualMachine because that aligns closely with what gcloud did.
• We don't publish the client for tpu.v2, so I had to generate our own binding from googleapis.

[justinsb]

This will probably replace #3810, as it seems to be easier to start from scratch than to pivot resources. I guess 3810 could become the V1 wrapper.