fix(@angular-devkit/build-angular): disable Worker wait loop for TS/NG parallel compilation in web containers

[clydin]

When using the application builder, a parallel TS/NG compilation is used that is run inside a Node.js Worker.
This Worker by default uses an Atomics-based wait loop to improve performance while waiting for messages. This
loop relies on the synchronous API receiveMessageOnPort. While this works well in Node.js, the web container
execution environment does not currently support passing transferable objects via receiveMessageOnPort. Attempting
to do so will cause a serialization error and a failed application build. To avoid this problem, the wait loop
optimization is disabled when the web container execution environment is detected. This change is only needed
for the TS/NG compilation as no other parallel operation within the build system currently uses receiveMessageOnPort
with transferable objects.

[d3lm]

Just to add some extra color here: I have tested the build with parallel compilation enabled and atomic loop disabled and it seems to work well in Chrome for both initial build and re-compilation. In Firefox the initial build also seems to work now, but it still gets stuck on re-compilation, but not always. Sometimes it worked. I am still trying to understand what's going on here. But at least the initial build now seems to work in Firefox as well.

[ngbot]

I see that you just added the action: merge label, but the following checks are still failing:
     status "mergeability" is failing
If you want your PR to be merged, it has to pass all the CI checks.
If you can't get the PR to a green state due to flakes or broken main, please try rebasing to main and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}