fix: check length of public key after decoding

[isoldo]

Pre-flight checklist

• I have read the Contributing Guidelines on pull requests.
• Commit messages follow the conventional commits spec
• If this is a code change: I have written unit tests.
• If this changes code in a published package: I have run pnpm changeset to create a changeset JSON document appropriate for this change.
• If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

Used PublicKey.fromString() as a validator for user input. As it turns out, the function doesn't check for length of the decoded public key.

Test Plan

Call PublicKey.fromString(baseEncode(publicKey)) with publicKey being a string with less than 32 characters - the function throws an error.

Related issues/PRs

#1114

[changeset-bot]

🦋 Changeset detected

Latest commit: 435d19d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 12 packages

Name	Type
@near-js/crypto	Patch
@near-js/accounts	Patch
@near-js/biometric-ed25519	Patch
@near-js/keystores-browser	Patch
@near-js/keystores-node	Patch
@near-js/keystores	Patch
near-api-js	Patch
@near-js/signers	Patch
@near-js/transactions	Patch
@near-js/wallet-account	Patch
@near-js/cookbook	Patch
@near-js/providers	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[andy-haynes]

Nice catch, thank you @isoldo for the contribution!

I have one minor comment inline but it's not a blocker. Let me know what you think but either way we'll get this into the next release.

[andy-haynes]

Thanks again @isoldo!