Pinging @elastic/es-core-infra (:Core/Infra/Build)

Debugging the tests themselves is already possible regardless of #48568 using the Gradle --debug-jvm option.

I think the actual ask here is for allowing testclusters to be debugged in a similar way to how we can debug when starting with the Run task.

I don't think IDEs will allow multiple debug connections from different JVMs, so we would need to configure different ports for different nodes and then users would pick where to connect, but definitely worth looking at the IDE support first.

another great improvement would be if we could pass properties to testcluster similarly to what we do with tests.es being passed to a run task.
This would for instance allow chaning the logging configuration when running a test. So for example if you want to run a test with trace logger level you need to modify a testCluster.integTest task in a module where testcluster is run from.

testClusters.integTest {
  setting 'logger.org', 'trace'
}

So it would be great if we could run it in this way for instance

./gradlew ':distribution:archives:integ-test-zip:integTestRunner' -
-tests "org.elasticsearch.test.rest.IntegTestZipClientYamlTestSuiteIT" 
-Dtests.method="test {p0=indices.get_field_mapping/20_missing_field/*}" 
-Dtests.seed=9C8E94BC31BDDC8B 
-Dtests.security.manager=true 
-Dtests.locale=fi 
-Dtests.timezone=Europe/Minsk 
-Dtestsclusters.es="logger.org=trace"