Tag OONI Pipeline v5 alpha

[hellais]

It's about time we stamp an alpha tag for OONI Pipeline v5.

Here is a checklist of what I would like to have done in order to call it an alpha.

Todo list

• [x] Polish the CLI and update relevant docs with the new CLI usage information
• [x] Refactor the activities and workflows (see temporalio/samples-python)
  • [x] evaluate idempotency of activities
  • [x] restructure workflows to properly encapsulate dependencies
• [x] Implement workflow scheduling (see sample)
• [x] More extensive testing and review of the analysis and fix any bugs found
  • [x] Reach 80% code coverage (we now have 87% coverage)

Stretch goals

• [ ] Land web connectivity 0.5 support: https://github.com/ooni/data/issues/39
• [ ] If we are happy enough with temporal, close https://github.com/ooni/data/issues/46
• [x] https://github.com/ooni/data/issues/65
• [ ] Add support for running on temporal cloud (currently blocking on getting our sponsored account activated by the temporal team)
• [x] https://github.com/ooni/data/issues/54
• [ ] https://github.com/ooni/data/issues/71

If the stretch goals are not completed, we should migrate them over to separate issues.

Useful references for best practices

• https://github.com/temporalio/samples-python/blob/main/cloud_export_to_parquet/workflows.py
• https://github.com/PostHog/posthog/tree/master/posthog/temporal

[hellais]

The open telemetry collection is working, however it sporadically logs errors as desired in the following issue: https://github.com/temporalio/sdk-python/issues/441

There is supposedly a workaround (https://github.com/open-telemetry/opentelemetry-python/issues/2606#issuecomment-1789515786), but I wasn't able to allocate enough time to fully investigate it.

I am going to proceed with landing the PR and consider addressing the bug with opentelemetry as part of future work.

[hellais]

Moved all pending tasks to separate tickets: https://github.com/ooni/data/issues/70 https://github.com/ooni/data/issues/71