Summary

Enhance the component test framework to optionally run tests against already-running local services instead of always starting new Maven processes with Quarkus dev mode. Currently, the framework automatically starts services in the background, which conflicts with developers' existing workflows when they already have services running locally (e.g., in dev mode with hot reload).

Why 

Developers are experiencing toil and friction with the current component test framework because:

• Workflow Conflicts: Can't run component tests when already developing with services running locally.
• Process Interference: The framework starts new Maven processes that conflict with existing dev mode sessions.
• Development Churn: Forces developers to stop their development workflow to run component tests.
• Hot Reload Disruption: Interferes with the iterative development process using Quarkus dev mode.

While the new framework has improved the developer experience by eliminating complex Python/IQE environment setup, it still lacks flexibility for common development scenarios.

Acceptance Criteria

• The component test framework detects when the target service is already running locally.
• The framework provides an option to run tests against the existing service instead of starting a new process.
• The default behavior remains unchanged (start the service if none is running) for backward compatibility.
• Clear error messages are provided when service detection fails or ports are in use.
• Documentation is updated with examples of running tests against existing services.
• Support for common local development ports (default Quarkus dev mode ports).
• Validation that the existing service is the correct service/version before running tests.
• The framework gracefully handles service discovery across different local configurations.