basalt-26.3: roachtest: cluster_creation failed

roachtest.cluster_creation [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_RedRoachtestNightlyGcePrivateBasaltBazel/21501600?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_RedRoachtestNightlyGcePrivateBasaltBazel/21501600?buildTab=artifacts#/restore/nodeShutdown/worker) on basalt-26.3 @ [e7c66e2d6a8b54db7183296be225c7e53d67b56d](https://github.com/cockroachdb/cockroach/commits/e7c66e2d6a8b54db7183296be225c7e53d67b56d):

```
test restore/nodeShutdown/worker failed: (test_runner.go:1087).func4: validating Basalt backing cluster teamcity-21501600-1788589738-02-n4cpu8-basalt storage: Basalt backing VM teamcity-21501600-1788589738-02-n4cpu8-basalt-0001 data disk 1 has volume type "pd-ssd", expected "hyperdisk-balanced" [owner=test-eng]
```

Parameters:
- MetamorphicBasaltMultiAZ=false
- cloud=gce
- coverageBuild=false
- cpu=8
- diskCount=0
- runtimeAssertionsBuild=false
Help

See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)

See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)

/cc @cockroachlabs/test-eng

[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*cluster_creation.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)

Read pkg/cmd/roachtest/README.md and inspect test_runner.go around line 1087. Use the restore/nodeShutdown/worker artifacts and the linked TeamCity failure to investigate why the Basalt backing VM reports pd-ssd instead of hyperdisk-balanced; done means the cluster_creation roachtest passes with the expected disk type.

Written by the indexing model from the issue text.