Lighten end-to-end workflows or remove them

[maximearmstrong]

Feature request

Currently, the end-to-end workflows test over 100 datasets at every commit. All datasets from the Mobility Database catalogs are also being tested for each commit excluding [acceptance test skip] in the commit message.

Since end-to-end workflows were created before the acceptance tests (partially after that conversation but even before here), we are wondering if they are still relevant now that the acceptance tests are in place. Originally, they were created to check that new code contributions do not break the validation process.

Proposed solution 3 potential solutions:

1. we remove them completely and use only the acceptance instead
2. Lighten the end-to-end workflows, but keep hardcoded URLs as it is right now.
3. Lighten them, but by sampling (say 5%) of the sources in the catalogs.

By lightening end-to-end workflows, but keeping them, users could push commits to PRs and have an overview of how the validation behave, while skipping acceptance tests.