test: make test-worker-prof more tolerant

[joyeecheung]

It seems after the recent V8 upgrade, it's no longer safe to assume there'll be 15 ticks per 1500ms. Lower it to 10 ticks.

This failed 19 PRs out of the last 100 CI runs in the latest reliability report.

Refs: https://github.com/nodejs/reliability/blob/main/reports/2025-10-15.md

[codecov]

Codecov Report

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

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #60272      +/-   ##
==========================================
- Coverage   88.57%   88.56%   -0.02%     
==========================================
  Files         704      704              
  Lines      208323   208323              
  Branches    40037    40037              
==========================================
- Hits       184531   184492      -39     
- Misses      15811    15856      +45     
+ Partials     7981     7975       -6     

see 34 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/69747/

[targos]

Note that it's already with the V8 update that the time was increased from 1000ms.
I don't understand this test enough to judge whether the numbers of ticks are still testing what we want.

[Hritikk999]

ALREADY REPORTED

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[joyeecheung]

I don't understand this test enough to judge whether the numbers of ticks are still testing what we want.

I think as long as the number is not 0, it's "working", though may be working terribly bad if it doesn't have enough sticks for users to understand the profile, but that's not really an issue for Node.js to fix, and flaking the Node.js CI with V8 profiling inefficacy doesn't really help anyone..

cc @addaleax

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[nodejs-github-bot]

Landed in 8429d9a