resource-agent or cli: check for unexpected instances

When running sonobuoy tests, if nodes from some previous test case (an earlier version of Bottlerocket, for example) are running in the cluster in addition to, or in place of, the intended nodes, then the results of the test are not accurate.

Can we, or should we, have a mechanism for ensuring that only the desired Bottlerocket nodes exist in the cluster before running sonobuoy?

Start by reviewing the resource-agent and cli components to understand where Sonobuoy tests begin and how intended nodes are identified. Define whether unexpected or missing Bottlerocket nodes should block testing, and consider the issue complete when that behavior is specified and verified.

Written by the indexing model from the issue text.