fix(repo): Ensure turbo cache is used properly for e2e tests

[BRKalow]

Description

Currently, args pass to turbo tasks are (understandably) included in the hash, and ultimately the cache key. As it relates to e2e tests, we pass a --project argument to the turbo task run, along with --only. What this means is turbo doesn't consider the task's dependencies when determining if the task has been cached or not.

This is problematic for us, as only the integration/ directory is included in the inputs. I've changed the command to not pass the --project arg, as it only has the chrome value today, and is otherwise unused. I also removed the --only flag. This should allow turbo to only re-run the integration tests if dependent packages have changed.

Checklist

• npm test runs as expected.
• npm run build runs as expected.
• (If applicable) JSDoc comments have been added or updated for any package exports
• (If applicable) Documentation has been updated

Type of change

• 🐛 Bug fix
• 🌟 New feature
• 🔨 Breaking change
• 📖 Refactoring / dependency upgrade / documentation
• other:

[changeset-bot]

⚠️ No Changeset found

Latest commit: 117f2d9

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

[BRKalow]

This would bust the build cache across tests against diff next versions, which we don't want.