Re-introduce test to verify that the VCH list API behaves properly when no VCH exists in the targeted compute resource

[mhagen-vmware]

removed in #7879 need to add it back in nightlies otherwise we can't do parallel jobs in CI

[zjs]

We could accomplish this several ways. For example, we could create an empty cluster or resource pool which we know is not used by other test. Alternatively, we could re-implement the test as a nightly test as suggested above — however this might complicate future efforts to parallelize those tests.

[zjs]

Once the test is introduced, we should revisit the Suite Teardown in 23-02-VCH-List (see #8082).

[renmaosheng]

@zjs any remaining work for this? thanks.

[zjs]

Yes; the test still needs to be re-introduced.

[zjs]

One approach would be to create a cluster as a part of the test (without any hosts), verify list works, and then delete the cluster. Another approach might be to move this to a scenario test.