The e2e tests have implicit dependencies
As reported by @albertvillanova for example, the following test does not pass

```
$ TEST_PATH=tests/test_11_api.py::test_rows_endpoint make test
```

while this ones pass:

```
$ TEST_PATH="tests/test_11_api.py::test_endpoint tests/test_11_api.py::test_rows_endpoint" make test
```

It's because `test_rows_endpoint` requires the parquet files to exist, and we implicitly rely on the fact that they have been created in `tests/test_11_api.py::test_endpoint`.

Other implicit dependency is when we test `is-valid` and `valid`.
The e2e tests have implicit dependencies: As reported by @albertvillanova for example, the following test does not pass

```
$ TEST_PATH=tests/test_11_api.py::test_rows_endpoint make test
```

while this ones pass:

```
$ TEST_PATH="tests/test_11_api.py::test_endpoint tests/test_11_api.py::test_rows_endpoint" make test
```

It's because `test_rows_endpoint` requires the parquet files to exist, and we implicitly rely on the fact that they have been created in `tests/test_11_api.py::test_endpoint`.

Other implicit dependency is when we test `is-valid` and `valid`.