Fix failing crypto tests

[MGibson1]

Type of change

- [x] Bug fix
- [ ] New feature development
- [ ] Tech debt (refactoring, code cleanup, dependency upgrades, etc)
- [ ] Build/deploy pipeline (DevOps)
- [ ] Other

Objective

Fixes failing crypto tests due to jestjs/jest#14379. This is accomplished through converting most of our usage of ArrayBuffer to Uint8Array, which works around the jest-environment-jsdom issue.

Uint8Array downcasts to ArrayBuffer without issues.

Before you submit

• Please add unit tests where it makes sense to do so (encouraged but not required)
• If this change requires a documentation update - notify the documentation team
• If this change has particular deployment requirements - notify the DevOps team
• Ensure that all UI additions follow WCAG AA requirements

[bitwarden-bot]

Checkmarx One – Scan Summary & Details – 40475c2f-0c21-4efe-85ae-ff8f37f46b51

New Issues

Severity	Issue	Source File / Package	Checkmarx Insight
	Use_Of_Hardcoded_Password	/libs/common/src/platform/services/web-crypto-function.service.spec.ts: 368	Attack Vector
	Use_Of_Hardcoded_Password	/libs/node/src/services/node-crypto-function.service.spec.ts: 285	Attack Vector
	Use_of_Broken_or_Risky_Cryptographic_Algorithm	/libs/node/src/services/node-crypto-function.service.ts: 23	Attack Vector

Fixed Issues

Severity	Issue	Source File / Package	Checkmarx Insight
	Use_Of_Hardcoded_Password	/libs/common/src/platform/services/web-crypto-function.service.spec.ts: 368	Attack Vector
	Use_Of_Hardcoded_Password	/libs/node/src/services/node-crypto-function.service.spec.ts: 305	Attack Vector
	Use_of_Broken_or_Risky_Cryptographic_Algorithm	/libs/node/src/services/node-crypto-function.service.ts: 23	Attack Vector

[differsthecat]

This looks good, I also verified locally the Native Test Runner is working as expected 👍

[ike-kottlowski]

Pulled branch and all test passed locally.