controller: support updown on same cluster

[webern]

Currently upgrade-downgrade testing (in which we launch a Bottlerocket instance, do an upgrade into a new version, then downgrade back to the original version) requires access to an EKS cluster that is exclusive. Sonobuoy conformance testing also requires exclusive access (and these exclusivity requirements may also apply to ECS as well).

Here's why:
Sonobuoy testing uses all the nodes on a cluster. So we need to make sure all of the nodes on the cluster are running the Bottlerocket OS that we want to test.
We can run conformance testing with a few nodes or we can run upgrade downgrade (updown) testing, but not both at the same time.

Let's say we are testing bottlerocket version 1.17.1 and the previous version is 1.17.0...

We want a way to model this (CRDs) and have the controller do the following:

• create cluster (if desired)
• run nodes for conformance testing of v1.17.1
• run conformance test
• terminate the nodes, but not the cluster
• run nodes of version 1.17.0
• run the updown test that will upgrade these to 1.17.1 and back to 1.17.0 and check them with sonobuoy quick

Then we will delete the test and resources.

We should be able to create all of these resource and test CRD objects at once, expressing the above desired execution path, and have the controller do it.

Note there may be additional exclusivity requirements for different/new testing modalities (see #TODO), but updown is a known/scoped case that we have before us now even before we write new test modalities such as #419 and #426.