Add isDeviceSupported method

[gtsonevv]

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

Test Plan

Related issues/PRs

[changeset-bot]

🦋 Changeset detected

Latest commit: 731d95c

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

This PR includes changesets to release 1 package

Name	Type
@near-js/biometric-ed25519	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]

Looks good overall, some questions inline

[andy-haynes]

Is there any way to check for support without side effects?

I see that the current implementation uses the response from createKey, so it's probably not a straightforward thing. But if you are aware of a less intrusive check it would be helpful to document in a comment or follow-up issue.

If this is the necessary approach however, would it be better to use a different key each time? I.e. is the outcome the same if the test-device key doesn't exist vs was previously created?

[gtsonevv]

After spending some time researching how to do this we found that the only way to do it was by using the response from createKey. The outcome should be the same after each call.

[andy-haynes]

Thank you for the clarification

[andy-haynes]

@race-of-sloths 🦥

[race-of-sloths]

@gtsonevv Thank you for your contribution! Your pull request is now a part of the Race of Sloths!
New Sloth joined the Race! Welcome!

Current status: executed

Reviewer	Score
@andy-haynes	3

The average score is 3

@gtsonevv check out your results on the Race of Sloths Leaderboard! and in the profile

What is the Race of Sloths

Race of Sloths is a friendly competition where you can participate in challenges and compete with other open-source contributors within your normal workflow

For contributors:

• Tag @race-of-sloths inside your pull requests
• Wait for the maintainer to review and score your pull request
• Check out your position in the Leaderboard
• Keep weekly and monthly streaks to reach higher positions
• Boast your contributions with a dynamic picture of your Profile

For maintainers:

• Score pull requests that participate in the Race of Sloths
• Engage contributors with fair scoring and fast responses so they keep their streaks
• Promote the Race to the point where the Race starts promoting you
• Grow the community of your contributors

Feel free to check our website for additional details!

Bot commands

• For contributors
  • Include a PR: @race-of-sloths include to enter the Race with your PR
• For maintainers:
  • Assign points: @race-of-sloths score [1/2/3/5/8/13] to award points based on your assessment.
  • Reject this PR: @race-of-sloths exclude to send this PR back to the drawing board.
  • Exclude repo: @race-of-sloths pause to stop bot activity in this repo until @race-of-sloths unpause command is called

[andy-haynes]

@race-of-sloths score 3

[andy-haynes]

🚢

[race-of-sloths]

🌟 Score recorded!

@andy-haynes, thank you for scoring this pull request in the Race of Sloths!

[race-of-sloths]

✅ PR is finalized!

Your contribution is much appreciated with a final score of 3!
You have received 40 (30 base + 10 weekly bonus) Sloth points for this contribution

Another weekly streak completed, well done @gtsonevv! To keep your weekly streak and get another bonus make pull request next week! Looking forward to see you in race-of-sloths