Use near-workspaces for the tests during the CI process

[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

Sometimes the CI node (https://rpc.ci-testnet.near.org/) does not respond to status requests causing all test that rely on it to fail. By moving to near-workspaces, the tests will be smoother and less likely to have problems. This transition aligns with best practices in test environment management and ensures that the CI process remains reliable and efficient.

Test Plan

All existing tests are passing.

Related issues/PRs

[changeset-bot]

⚠️ No Changeset found

Latest commit: df0cd87

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

[vikinatora]

Merge conficts have to be resolved, other than that looks good.