test: add retry logic for eventloopdelay histogram sampling

[mcollina]

Summary

Fixes flaky test-performance-eventloopdelay test on sharedlibs builds.

Problem

On some build configurations (e.g., Ubuntu 24.04 sharedlibs), the histogram may not record valid samples (min > 0) after the initial spinning period. The test fails with:

AssertionError [ERR_ASSERTION]: assert(histogram.min > 0)

The previous fix (PR #61629) added setImmediate to allow samples to be recorded, but this wasn't sufficient for all configurations.

Solution

Add a retry mechanism that checks if valid samples have been recorded (count > 0 && min > 0 && max > 0). If not, the test will spin the event loop additional times (up to 3 retries) before asserting.

This ensures the test passes on slower or differently-configured systems where event loop delay sampling may take longer to produce measurable results.

Verification

Tested locally with python3 tools/test.py --repeat 30 - all passed.

Refs: nodejs/reliability#1461

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.71%. Comparing base (4a13a62) to head (64c291a).
⚠️ Report is 14 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #61796      +/-   ##
==========================================
- Coverage   89.76%   89.71%   -0.05%     
==========================================
  Files         675      675              
  Lines      204674   204797     +123     
  Branches    39330    39348      +18     
==========================================
+ Hits       183716   183734      +18     
- Misses      13235    13336     +101     
- Partials     7723     7727       +4     

see 52 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.