Provide a way to parallelize OPA tests automatically

[ArnaudBuchholz]

Is your feature request related to a problem? Please describe. Parallelizing OPA tests requires a structural change to the project.

Describe the solution you'd like QUnit organizes the tests using module. A deep probing of the OPA test would allow the listing of existing modules. Then, we could have as many runs as required to execute each module individually (meaning the other modules would be 'turned off')

Describe alternatives you've considered Structural change of the project can be challenging on some projects.

Additional context

[ArnaudBuchholz]

In order to build a POC :

• [x] Provide a way in training-ui5con18-opa to have all OPA journeys added as once (could be a URL parameter)
• [x] Improve the add-test-pages endpoint to distinguish calls from suite and calls from qunit pages
• [x] Improve probing to list the existing modules in an OPA page before executing them
• [x] See how modules are uniquely identified (I believe qUnit generates an ID for each)
• [x] Generate as many test pages as the number of modules with specific parameters to restrict the execution of one module
• [x] See how to enable the execution of one module only in qUnit (we should be able to leverage the hooks)
• [x] What about the report, should we aggregate all modules execution under one page or is it acceptable to report on as many pages ?

[ArnaudBuchholz]

QUnit already supports a moduleId selector : http://localhost:8080/test/integration/opaTests.qunit.html?moduleId=5201787c runs Search journey in training-ui5con18-opa

[ArnaudBuchholz]

To make it work, it requires that probing of testsuite.qunit.html goes through probing again for added test pages.

[ArnaudBuchholz]

 --split-opa option added and tested successfully