workers: make Worker async disposable

[jasnell]

await using worker = new Worker(...);

[nodejs-github-bot]

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.24%. Comparing base (20c4b80) to head (658a86f).

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #58385      +/-   ##
==========================================
+ Coverage   90.23%   90.24%   +0.01%     
==========================================
  Files         633      633              
  Lines      186883   186888       +5     
  Branches    36695    36688       -7     
==========================================
+ Hits       168632   168656      +24     
+ Misses      11040    11039       -1     
+ Partials     7211     7193      -18     

Files with missing lines	Coverage Δ
lib/internal/worker.js	99.82% <100.00%> (+<0.01%)	⬆️

... and 21 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.

[LiviaMedeiros]

LGTM with or without the nit; and s/^workers/worker/ in the commit message.

Noting that the code change can be safely backported to release lines that have Symbol.asyncDispose but not the ERM itself; and splitting this into two commits (one that adds [SymbolAsyncDispose](), tests it by calling explicitly, and documents without code example; and another for v24+ adding using in tests in docs) might make it more straightforward for releasers.

[LiviaMedeiros]

Nit: was w meant to be checked after the scope? If not, we don't really need it.

Suggested change

	let w;
	{
	// Verifies that the worker is async disposable
	await using worker = new Worker('for(;;) {}', { eval: true });
	w = worker;
	w.on('exit', common.mustCall());
	}
	{
	// Verifies that the worker is async disposable
	await using worker = new Worker('for(;;) {}', { eval: true });
	worker.on('exit', common.mustCall());
	}

[aduh95]

Why dont-land-on-v22.x PRs that should not land on the v22.x-staging branch and should not be released in v22.x. ? That feels like something we'd want to backport. Could you follow the same approach of #58206, i.e. avoid using the new syntax so this can be backported, and add a TODO to have a follow-up to test with the await using syntax?

[mcollina]

lgtm