refactor: establish Crypto folder feature

[jderochervlk]

Tracking issue: #342

Stack context

Part 7 of the Option 5 folder-feature stack.

• Previous: refactor: establish ViewTransitions folder feature #316
• Next: another dependency-clean domain folder

Review this PR as the incremental diff against #316.

Summary

• rename src/WebCrypto to the target src/crypto folder
• change the folder to the unqualified internal Crypto feature
• add the supported WebAPI.Crypto feature with its WebAPI.DOM dependency
• preserve the flat WebAPI.Crypto and WebAPI.SubtleCrypto modules

The internal WebCryptoTypes helper remains private inside the complete folder.

Temporary state

• this PR does not introduce compatibility aliases, file exclusions, or module slices; the Crypto folder and feature ownership are final
• the typed-array helper it uses remains in core until the final ownership cleanup determines whether that broadly shared type should stay foundational

Review focus

• the WebAPI.Crypto -> WebAPI.DOM + Crypto implication
• unchanged public Crypto APIs and module paths
• complete folder ownership

Verification

• node_modules/.bin/rescript clean
• node_modules/.bin/rescript build --prod --features DOM,Crypto
• npm run build
• npm test
• npm run format:check
• git diff --check

[jderochervlk]

@codex

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ac809614fc

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Make the advertised Crypto feature compile

When a consumer selects WebAPI.Crypto, rescript build --prod --features WebAPI.Crypto fails because this implication activates the entire WebAPI.DOM source group, while its dependencies do not provide modules such as EventTarget and DOMStringMap used by that group. The compiler help confirms that --features includes transitively implied features, so the new public feature is unusable unless this dependency points at the appropriate internal foundation or supplies the complete DOM prerequisite closure.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Update the docs feature map for the renamed folder

After this rename, scripts/unmonorepo/feature-spec.mjs still describes the feature directory as WebCrypto. Consequently, docs/utils.js searches for src/WebCrypto/WebCryptoTypes.res and filters the API module out when that path does not exist, so the Crypto documentation disappears from the generated API pages. Update the shared feature specification to recognize the new directory while retaining the intended public naming.

Useful? React with 👍 / 👎.