[Bug]: New-HolodeckInstance fails with -DeveloperMode when Cluster has limited view or resource pool

Holorouter Version

9.1

VCF Version

VCF 9.1

Target Type

vCenter Cluster

Describe the bug

Similar to #140, but when deploying New-HolodeckInstance with all appropriate env vars set, including $env:cluster_name = "MY-CLUSTER" the deployment fails with error:

PreChecks[1101]: [ERROR] Failed to verify target host hardware details.
PreChecks[1101]: [ERROR] Cannot process argument transformation on parameter 'Cluster'. Cannot convert value to type System.String.
PreChecks[1101]: [ERROR] Failed to complete Pre-Checks.

This likely happens when a Cluster has a user with limited permissions on it or a Resource Pool. As the table output with Cluster and ResourcePool objects displays multiple entries for the Cluster with the given name.

Per #140 it looks like a Resource Pool can now be selected, but is this exposed via an env var for -DeveloperMode and documented?

Reproduction steps

1. Create a vSphere Cluster in vCenter and a user with limited permissions on it
2. Set appropriate env vars for your environment per docs
3. Attempt a New-HolodeckInstance deployment with -DeveloperMode

Expected behavior

The deployment works using the first named instance of the Cluster found, or fails as expected and an env var is exposed for Resource Pool or Cluster MOID or similar?

Relevant logs

Additional context

No response