Run long-running tests on a periodic basis

[echeran]

For collator and/or normalizer components, there are fuzz tests that are long-running but not included in the cargo test set of tests, or in #2039 the conformance tests are not actually included in the repo to save space in the repo, but those can be downloaded and then the tests can be run with the actual input.

We should probably create a workflow for the long-running tests, and then configure that workflow to run periodically once in a while (frequency TBD) on main.

[echeran]

If we have a separate workflow, then we can configure it to run periodically in a cron job manner. Even if fuzz tests run for 24+ hours, we can run this workflow with a period size >> 24+ hrs (ex: 1 week). Perhaps make it start running early Saturday morning since weekends would have less demand for available slots for running CI jobs in Github Actions from people working on PRs.

[robertbastian]

The full datagen CI is a candidate for this as well, it already takes half an hour and will become even slower with #2058.