By having the e2e tests inside fuels we're prone to useing stuff from fuels dependencies rather than fuels itself. This then leads to issues like "we didn't know xyz hadn't been reexported throught fuels. The test worked fine" only to find that we included xyz from something like fuel-tx in the test.

This cannot be avoided as long as the tests are in fuels because we cannot make prod deps unavailable for the integration tests.

One idea is to have a new e2e (or whatever) package that would contain all the e2e tests. The package itself should not be published. The tests there would only be dependent on fuels.