[SUREFIRE-2048] Reworking the hack in SUREFIRE-1535. Fork should received command declaring Java type of the test.

**[Tibor Digana](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tibor17)** opened **[SUREFIRE-2048](https://issues.apache.org/jira/browse/SUREFIRE-2048?redirect=false)** and commented

This is very important issue for TestNG and JUnit5/Cucumber.
Currently, the plugin sends a string to a fork with FQN of test class.
This mechanism should be extended with other possibilities like TestNG suite XML path, JUnit5 unique id, etc.

---

**Issue Links:**
- [SUREFIRE-2073](https://issues.apache.org/jira/browse/SUREFIRE-2073) Test class filtering should be done in the particular fork JVM where the real test would run.
(_**"blocks"**_)
- [SUREFIRE-1560](https://issues.apache.org/jira/browse/SUREFIRE-1560) Rework SUREFIRE-1535. Use only FORKTESTSET and split SurefireProvider to two interfaces - currently has two responsibilities
(_**"is duplicated by"**_)

Start by reading SUREFIRE-1535 and the linked SUREFIRE-2073 and SUREFIRE-1560 issues to understand the existing fork command and split responsibilities. Done means the fork receives a command that declares the Java test type and supports the stated TestNG suite XML path and JUnit5 unique ID cases.

Written by the indexing model from the issue text.