feat: replaces the js-sha256 library with @noble/hashes

[krpeacock]

Description

Due to an ongoing incident where the js-sha256 library is breaking on new versions of Chrome, we are replacing it with the industry standard library, @noble/hashes

This is a compact, audited, pure JS library, and it is able to produce hashes synchronously, which makes it easier to drop into our library than the WebCrypto.subtle.digest api, which is promise-based.

Fixes # (issue)

How Has This Been Tested?

Updates to a few unit tests, and running against existing golden canonical hashes and e2e test suite

Checklist:

• My changes follow the guidelines in CONTRIBUTING.md.
• The title of this PR complies with Conventional Commits.
• I have edited the CHANGELOG accordingly.
• I have made corresponding changes to the documentation.

[github-actions]

size-limit report 📦

Path	Size
@dfinity/agent	86.96 KB (-2.51% 🔽)
@dfinity/candid	13.52 KB (-12.69% 🔽)
@dfinity/principal	5.15 KB (-23.91% 🔽)
@dfinity/auth-client	92.54 KB (-2.48% 🔽)
@dfinity/assets	89.56 KB (-2.34% 🔽)
@dfinity/identity	89.81 KB (-2.35% 🔽)
@dfinity/identity-secp256k1	232.06 KB (+0.66% 🔺)

[keplervital]

I can confirm that moving to use @noble/hashes fixes the issue i was having on Chrome Version 116.0.5845.96 (Official Build) (arm64).

[rsundar01]

I took a look at the code updates and it seemed pretty straightforward. I don't have any major feedback. Perhaps, it would help to wrap the crypto impl details that would help to localize the changes.