FTR simulate mocha dry run

[pheyos]

Summary

This PR works around a bug in mocha's dry run execution by collecting the tests without actually running mocha.

Details

• This is a follow-up on FTR support mocha dry run #125915
• It still uses the same output file
• The created report structure is close to the json reporter output, just left away some execution specific fields:
  
  
• Tested locally with the whole api_integration suite and with the whole functional suite to make sure it works for many entries

[spalger]

LGTM, glad to see this wasn't too hard to implement and that you were able to keep it isolated so we can just remove it once Mocha fixes their implementation 👍

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 8e0d6b0
• Storybooks Preview
• Webpack Bundle Analyzer

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
@kbn/test	205	208	+3

Any counts in public APIs

Total count of every any typed public API. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats any for more detailed information.

id	before	after	diff
@kbn/test	5	6	+1

Unknown metric groups

API count

id	before	after	diff
@kbn/test	241	244	+3

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @pheyos

[kibanamachine]

💔 Some backports could not be created

Status	Branch	Result
✅	8.1
❌	7.17	Backport failed because of merge conflicts
✅	8.0

How to fix

Re-run the backport manually:

node scripts/backport --pr 126702

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

[pheyos]

💚 All backports created successfully

Status	Branch	Result
✅	7.17

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation