chore: remove near-api-js tests

[andy-haynes]

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

As part of the migration to @near-js packages, tests were copied into the new packages but also remained in the near-api-js package. The original tests provided a sanity check to ensure that test coverage was unaffected by the transition, and so have now fulfilled their purpose.

I've left the test harness in place should there be a need for new tests, but I don't expect this to happen.

As an added bonus there is no longer contention between the duplicate accounts tests, allowing tests to be run in parallel for massive time savings.

[changeset-bot]

⚠️ No Changeset found

Latest commit: aa4f79e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[morgsmccauley]

Nice one!