[Enhancement] Support for Cluster Configuration and Cleanup in Smoke Test Framework

[zelinh]

Is your feature request related to a problem? Please describe

The smoke test framework is currently designed to:

• Deploy a single cluster with default configurations at the start of the test run.
• Execute all test cases across different testing components on this single cluster without intermediate cleanup.

This design requires that:

• Test cases for all components must avoid conflicts with one another.
• More detailed or potentially conflicting test scenarios are deferred to the functional or integration test frameworks.

Describe the solution you'd like

To increase the flexibility of the smoke test framework and support more diverse test cases, we propose enhancing the framework to include the following features:

1. Customized Cluster Configurations:
   Allow testing components to specify custom cluster configurations tailored to their requirements. This would enable test cases to better simulate real-world scenarios.

2. Cluster Cleanup Between Components:
   Introduce the ability to clean up and reset the cluster after completing each testing component, ensuring that:

• Subsequent tests are isolated and unaffected by prior states.
• Conflicting test scenarios can be run safely within the smoke test framework.

Describe alternatives you've considered

No response

Additional context

No response