chore: use common WASM builder

[mhdawson]

This relates to...

See discussion in #3714

Note that with the updated common/container the same WASM seems to be generated so there should be
no functional changes.

The container itself is build using an approach that was based off of what undici was doing.

Rationale

#3714 includes the rational and discussion agreeing that I should submit a PR.

Changes

Updates the build process to use the Node.js common wasm-builder container.

Features

Bug Fixes

Breaking Changes and Deprecations

Status

• I have read and agreed to the Developer's Certificate of Origin
• Tested
• Benchmarked (optional)
• Documented
• Review ready
• In review
• Merge ready

[mhdawson]

Rebased

[mhdawson]

Since the WASM did not change I don't think any of the failures are related to this PR.

This issue seems to say there is a lot of flakiness and probably confirms that - #3787

[metcoder95]

Are there plans to provide regular updates to it?

[mhdawson]

I have been thinking a bit about that, I think we want to update regularly but not necessarily too often. At least a month before every new Node.js major but I could see more often making sense as well.

The repo where it is maintained has release please and all of the automation to generate a new vesion so it's as simple as a PR to update the dockerfile used to build the container and once that lands the rest is pretty much automated.

@metcoder95 how often do you think an update would make sense ? How often was undici updating?

[metcoder95]

I cannot develop a cadence, as I'd say that should be up to the things added to the new version. If it contains security fixes, maybe faster than usual, otherwise we can make a check every time we prepare a new undici's release.

@mcollina @ronag wdyt?