fix(plugin-workspace-tools): properly report errors for all non-zero exit codes

[kumavis]

What's the problem this PR addresses?

yarn workspaces foreach [...] does not clearly indicate that there was a failure, or for what workspace there were non-zero exit codes.

Before: (just says "done", but exit code is 1)

Done in 57s 886ms

endo3 on  yarn-workspaces-for-scripts [!?] via  v18.20.4 took 58s 
❯ echo $?
1

After:

The command failed in workspace ses@workspace:packages/ses
Failed with errors in 45s 837ms

How did you fix it?

I used the report.reportError feature to report all the workspaces that had non-zero exit codes.
The final exitCode is not changed in this PR.

Checklist

• I have read the Contributing Guide.
• I have set the packages that need to be released for my changes to be effective.
• I will check that all automated PR checks pass before the PR gets reviewed.

🙏 @arcanis thank you for yarn 🙏

[kumavis]

we no longer need to set the finalExitCode here bc the resulting error code will be set to 1 by report.exitCode() since errors have been reported.

berry/packages/yarnpkg-core/sources/StreamReport.ts

Lines 267 to 269 in 80052a0

	exitCode() {
	return this.hasErrors() ? 1 : 0;
	}

[kumavis]

one CI failure... looks like a flakey test? unable to diagnose https://github.com/yarnpkg/berry/actions/runs/11171437408/job/31056182006

possibly related to nodejs/node#51766 ?

this unrelated recent CI run passes but logs this:

A worker process has failed to exit gracefully and has been force exited. This is likely caused by tests leaking due to improper teardown. Try running with --detectOpenHandles to find leaks. Active timers can also cause this, ensure that .unref() was called on them.

All tests are passing, but force closing the worker is failing

[kumavis]

(rebased)

[kumavis]

@arcanis let me know if this PR requires any adjustments