test: always run sync tests

[gakonst]

Enables running the sync tests introduced in #913 on CI by moving them under the test/ directory.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 47a4a1a

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

[codecov-commenter]

Codecov Report

Merging #989 (47a4a1a) into develop (5a79849) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #989   +/-   ##
========================================
  Coverage    82.21%   82.21%           
========================================
  Files           48       48           
  Lines         1895     1895           
  Branches       303      303           
========================================
  Hits          1558     1558           
  Misses         337      337           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5a79849...47a4a1a. Read the comment docs.

[platocrat]

i'm updating the branch here

[tynes]

I like the idea but it looks like the path to the docker-compose.yml is incorrect

[annieke]

this is where i want to eventually move to! i think 2 issues right now:

1. running the tests in docker also gives me this spawn docker-compose ENOENT error locally, which i think is from trying to use docker-compose within docker. haven't tried too hard to debug it, because
2. sync tests will always fail when ran with integration tests right now, since erc20 deploys + transfers produce mismatched stateroots
   so as of now the simplest way is still to run sync tests in their own workflow, i'll try out the other solution to see if it's faster feat[ci]: parallelize integration, example, and sync tests #972 (comment)

[gakonst]

Closing given Annie is on it. I think we should figure out what causes the mismatched state roots before enabling the tests (independently of having it in the same or other workflow, since otherwise the test would give us false confidence)