feat: Add WebCrypto wrappers for SHA hashing

[FrederikBolding]

Explanation

Add wrappers for native SHA-256, SHA-512 and SHA-384 to metamask/cryptography.

References

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

Note

Low Risk
Isolated new hashing wrappers over the platform Web Crypto API with unit tests; no changes to existing consumer auth or key-handling flows in this diff.

Overview
Replaces the @metamask/cryptography placeholder with async SHA helpers (sha256, sha384, sha512) that wrap globalThis.crypto.subtle.digest and accept any BufferSource, returning digests as Uint8Array. The package entrypoint now re-exports ./sha.js instead of the sample greeter.

Adds Jest coverage for each algorithm across Uint8Array, ArrayBuffer, and DataView inputs (using @metamask/utils in tests only), documents the initial release in the changelog, and wires TypeScript project references plus the README dependency graph to @metamask/utils.

^{Reviewed by Cursor Bugbot for commit 0465a77. Bugbot is set up for automated code reviews on this repo. Configure here.}

[Mrtenz]

Do we not want a fallback in case WebCrypto is not available?

[FrederikBolding]

My thinking with the cryptography package was to not have fallbacks. Instead expecting the clients have WebCrypto available.

[Mrtenz]

If you change the functions to allow BufferSource, adding some tests with other byte array representations here would be good.

Also alphabetic sorting.