Goal: 

Reduce CI configuration and its maintenance by whitebox obtaining information.

The `neutron-whitebox-tempest-plugin` [0] assumes computes/controllers can be connected for various test needs already.

This allows to reduce configuration and its maintenance by actively obtaining information from any pod/container on any node needed within used setup.

As raised and discussed in slack thread [1] from review comment [2].

This story should contain a few tasks to address each specific configuration case commonly used throughout `neutron-whitebox-tempest-plugin`.

Acceptance Criteria:

The idea is to replace most possible cases of `CONF` read (maintained in CI) by automated checks on setup nodes - more specifically methods actively obtaining the information in base classes to allow use in inheriting test classes.

Example:

Instead of using configuration read for compute amount in setup, such as `CONF.compute.min_compute_nodes > 1` and its maintenance in lots of jobs in `ci-framework-jobs` or `rhos-qe-jenkins`, use code like this [3] and more checking methods like `is_setup_single_compute`.

[0] https://opendev.org/x/whitebox-neutron-tempest-plugin 

[1] https://redhat-internal.slack.com/archives/C046JULBVJ7/p1744704355866519?thread_ts=1744267516.455549&cid=C046JULBVJ7 

[2] https://review.opendev.org/c/x/whitebox-neutron-tempest-plugin/+/947190/comment/91ce0be3_a92aaf8f/ 

[3]

`

if self.is_setup_single_compute():
    raise self.skipException('Test needs more than 1 compute')

`