Add emsdk 6.0.6

[fpelliccioni]

• Added emsdk/6.0.6 alongside 5.0.3, and updated the profiles to match it.
• Added a pre-commit check that keeps compiler.version and the [tool_requires] emsdk version in sync (Keep compiler.version and used emsdk version consistent #10).
• Documented that wasm64 with emsdk 6 wants Conan 2.31.0+, which emits the modern -m64 instead of the deprecated -sMEMORY64 (Fix deprecation warning when building with emscripten 6.0.1 or higher conan#20152). required_conan_version is left alone: the recipe is shared with 5.0.3, where -sMEMORY64 is still correct, and wasm32 is unaffected.
• emsdk/6.0.6 bundles node 24.19.0, so the wasm64 "install node 23+ by hand" caveat now applies to the 5.x series only.

Checked from an empty CONAN_HOME with Conan 2.31.2 on Linux x86_64:

$ conan create recipes/emsdk/all --version=6.0.6 --build=missing
emcc -v -> 6.0.6 (ce75e06884093bcefb86a6b8fd56a5d62a4cc245)
node -v -> v24.19.0

A probe binary built and ran with both profiles: wasm32 reports sizeof(void*)=4, wasm64 reports 8, using the SDK's own node and with no deprecation warning. The generated conan_toolchain.cmake carries -m64.

5.0.7 also exists upstream and is newer than the 5.0.3 here; left untouched to keep this to one version.

[CLAassistant]

All committers have signed the CLA.

[memsharded]

Thanks very much for the contribution @fpelliccioni

Maybe this is doing too much, and might be split into 2 different PRs:

• One thing is the new version of emsdk, that needs some changes
• And a different one is the new CI check emsdk consistency script (pre commit hook)

Is the second one strictly necessary, or a convenience? Adding too much stuff to this repo CI is not planned, on the contrary, this repo should try to have a CI as lean as possible.

But just my opinion, @jcar87 might think differently

[fpelliccioni]

Thanks very much for the contribution @fpelliccioni

Maybe this is doing too much, and might be split into 2 different PRs:

• One thing is the new version of emsdk, that needs some changes
• And a different one is the new CI check emsdk consistency script (pre commit hook)

Is the second one strictly necessary, or a convenience? Adding too much stuff to this repo CI is not planned, on the contrary, this repo should try to have a CI as lean as possible.

But just my opinion, @jcar87 might think differently

Fair point, split it. Force-pushed to a4ef13b, now just the 6.0.6 bump.

The check and the hook are out, and .pre-commit-config.yaml is back to what's
on main so it's not in the diff.

It was a convenience. No workflows in this repo, so it only ran if you had
pre-commit installed locally, and it hardcodes the emsdk paths anyway. The
underlying issue is real (compiler.version and tool_requires have to match or
package ids stop tracking the SDK), but #10 can stay open for that. Happy to
propose it separately if you and @jcar87 want it.

Checked by hand: profile 6.0.6, tool_requires 6.0.6, published in config.yml,
sha256 in conandata.

[memsharded]

Looks good to me, thanks!