feat: add sha384, sha512 support

[lukasjhan]

No description provided.

[Copilot]

Pull Request Overview

This PR adds SHA-384 and SHA-512 support alongside the existing SHA-256 implementation.

• Introduces sha384 and sha512 functions and extends hasher to handle those algorithms.
• Updates tests to compare all three algorithms against Node’s crypto.createHash.
• Bumps the @noble/hashes dependency to ^1.8.0 and re-exports from a consolidated sha2.ts.

Reviewed Changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 1 comment.

File	Description
packages/hash/src/test/sha2.spec.ts	Renamed suite, added browser-skipped tests for SHA-256/384/512 on strings and ArrayBuffers
packages/hash/src/sha2.ts	Added sha384, sha512 and updated hasher with a switch; adjusted imports
packages/hash/src/index.ts	Updated export from sha256 to sha2
packages/hash/package.json	Bumped @noble/hashes from 1.0.0 to ^1.8.0

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

Comments suppressed due to low confidence (2)

packages/hash/src/sha2.ts:8

• The function currently accepts ArrayBuffer but normalizes to Uint8Array internally. Consider updating the signature to (text: string | Uint8Array) to accurately reflect the input shape and avoid type mismatches.

export const sha256 = (text: string | ArrayBuffer): Uint8Array => {

packages/hash/src/test/sha2.spec.ts:128

• There’s no test covering an unsupported algorithm in hasher. Adding a test that calls hasher(data, 'invalid-algo') and expects the Unsupported algorithm exception would ensure correct error handling.

describe('Hash', () => {

[cre8]

@lukasjhan I think when we rename the one file + make clear that someone could also use their own hasher implementation, than this PR is fine.