Orchestrator sometimes runs all the instances of a parameterized test in the same process

[PhilGlass]

Description

Orchestrator has a fast path that skips test discovery if the test target is a single method:

android-test/runner/android_test_orchestrator/java/androidx/test/orchestrator/AndroidTestOrchestrator.java

Lines 259 to 262 in dd62f39

	if (isSingleMethodTest(classArg)) {
	Log.i(TAG, String.format("Single test parameter %s, skipping test collection", classArg));
	callbackLogic.addTest(classArg);
	runFinished();

This doesn't work for parameterized tests, since even a single method target may expand to any number of parameterized test instances.

Steps to Reproduce

Run a parameterized test method through test orchestrator. They will all run in the same process. You can verify this by logging the PID.

Expected Results

Each instance of the parameterized test runs in its own process.

Actual Results

All of the instances of the parameterized test run in the same process.