tools: optimize wildcard execution in tools/test.py

[joyeecheung]

Previously for each matching test, it would execute multiple node -p commands to decide the configurations of the executable. That means if there are 100 tests matched, it will run the Node.js executable 4*100 times to retrieve the same configurations repeatedly. This changes the loop order so that it only execute these commands once and reuse the results for all matching tests.

[joyeecheung]

$ time tools/test.py test/*/test-stream-*
[00:02|% 100|+ 174|-   0]: Done

All tests passed.

User time: 5.20s
System time: 2.24s
CPU time: 187%
Total time: 3.96s

$  git checkout main

$ time tools/test.py test/*/test-stream-*
[00:02|% 100|+ 174|-   0]: Done

All tests passed.

User time: 16.66s
System time: 7.76s
CPU time: 81%
Total time: 30.10s

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.56%. Comparing base (db0121b) to head (ffcb94c).
⚠️ Report is 42 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #60266      +/-   ##
==========================================
+ Coverage   88.53%   88.56%   +0.02%     
==========================================
  Files         704      704              
  Lines      208087   208322     +235     
  Branches    40010    40034      +24     
==========================================
+ Hits       184239   184496     +257     
+ Misses      15866    15862       -4     
+ Partials     7982     7964      -18     

see 69 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/69757/