An InstanceGroups with multiple zones can have duplicate node names on GCE

/kind bug

**1. What `kops` version are you running? The command `kops version`, will display
this information.**

Client version: 1.33.1 (git-v1.33.1)

**2. What Kubernetes version are you running? `kubectl version` will print the
version if a cluster is running or provide the Kubernetes version specified as
a `kops` flag.**

**3. What cloud provider are you using?**

**4. What commands did you run? What is the simplest way to reproduce this issue?**

**5. What happened after the commands executed?**

On GCE, kOps creates a MIG per zone, so nodes in different zones can potentially have the same name.

**6. What did you expect to happen?**

**7. Please provide your cluster manifest. Execute
`kops get --name my.example.com -o yaml` to display your cluster manifest.
You may want to remove your cluster name and other sensitive information.**

```yaml
```

**8. Please run the commands with most verbose logging by adding the `-v 10` flag.
Paste the logs into this report, or in a gist and provide the gist link here.**

**9. Anything else do we need to know?**

Start by tracing kOps's GCE InstanceGroup and managed instance group node-name generation across multiple zones. Reproduce the reported case if possible, then verify that nodes created in different zones receive distinct names; the issue currently provides no manifest, logs, commands, or named tests.

Written by the indexing model from the issue text.