feat: pythonic scenario tests (trials)

[redpanda-f]

No description provided.

[redpanda-f]

Todo:

• && (github.event_name == 'schedule' || github.event_name == 'workflow_dispatch') needs to be added, so issues are not created with PRs
• REPORT_ON_SUCCESS: 'true' so we do not have issues on success

before merge

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[BigLep]

A couple of things when looking at #75

1. Can we include the synapse commit that was used as well?
2. (nit) Status has a period after it "Status." We can remove the period
3. For versions info, at the minimum can we remove the prefix that is in the log messages (e.g., "�[32m INFO�[0m �[2msrc/main_app/version.rs�[0m�[2m:�[0m�[2m19:�[0m "). (Even better is just to get it to a simpler bullet list or table, but that's not essential.)
4. CI run link: can we link directly do the corresponding "job" rather than just to the "run". For example, link to the stability job.
5. For the test summaries, can we link to the corresponding step as well? For example,I would expect to see a URL with an anchor like #step:39:26 (e.g., https://github.com/FilOzone/foc-devnet/actions/runs/22752589844/job/65990079825#step:39:27)

[BigLep]

A couple of things:

1. I assume a better PR description will be provided
2. I was also wondering about how to break this down into smaller units so parts can start getting merged in smaller chunk. I could imagine a PR for the "latesttag" functionality. Maybe another for the githooks and linting, and then the main PR that adds the scenarios?
3. I assume we need to add some README_ADVANCED docs about "latesttag"?