Move componentize-js to the lann fork and adopt its eager-settlement fix

[lann]

Two co-dependent steps, one ruling: componentize-js is now sourced from
the lann/componentize-js fork, at a pin that includes the fork's fix.

Repoint references — the toolchain workflow's clone URL, the library
and demo READMEs, and the shim header now name lann/componentize-js
(a fork of dicej/componentize-js). Deliberately unchanged: the
dicej/componentize-js#5 citation (the PR lives on the parent repo; the
fork has no PR 5) and the "(dicej's ComponentizeJS reboot)" provenance
attributions in AGENTS.md / js/componentize/justfile.

Bump the pin to f417fa6d5f74, the fork's head: it merges
lann/componentize-js#1,
which routes the eager (returned-immediately) async-import path through
the same ok/err discrimination as the suspending path, so result<>-typed
imports settle spec-shaped instead of resolving with the raw
{ tag, val } wrapper. This library already normalized both settlement
shapes (callImport), so its behavior is unchanged — the README's
"upstream quirk" paragraph and the callImport doc now describe the fix
as included in the pin. The bump is what makes the fix available to
consumers without such normalization, e.g. the websocket sibling's shim
(see polymorph-components/polymorph-websocket#31).

The bump depends on the repoint: f417fa6 is reachable only from the
fork, so the workflow's clone must already name it.

Toolchain mechanics: the workflow built and published the (rev, platform)
assets from this branch, and just componentize::update-toolchain-digest
recorded their digests after verifying the build-provenance attestations
(subject digest, building repository, and workflow path all checked).

Verified locally on the new toolchain: just componentize::test (19/19
checks) and just wpt::test (all in-subset groups pass; census
unchanged, so no wpt::update-expectations needed).