feat(test): fix core and react test issues

[gershon]

Description

• fix cyclic dependency between @ark-project/core and @ark-project/test
• use vitest for core tests (already used for react tests)

What type of PR is this? (check all applicable)

• 🍕 Feature (feat:)
• 🐛 Bug Fix (fix:)
• 📝 Documentation Update (docs:)
• 🎨 Style (style:)
• 🧑‍💻 Code Refactor (refactor:)
• 🔥 Performance Improvements (perf:)
• ✅ Test (test:)
• 🤖 Build (build:)
• 🔁 CI (ci:)
• 📦 Chore (chore:)
• ⏩ Revert (revert:)
• 🚀 Breaking Changes (BREAKING CHANGE:)

[linear]

DEV-819 Fix v2 core tests issues

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4232235

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

[kwiss]

I think we shouldn't use environment variables for accounts but instead use a config file that goes with our testing environment. It looks like we'll use Starknet devnet instead of Dojo Katana, so in that regard, we can use their seed with a specific value so anyone using the seed can run the tests.