Consolidate Github workflows

[Diolor]

We may use workflows slightly more efficiently.
Now 1 workflow = 1 job.

A more effective architecture is 1 workflow (per use case/goal) = 1 or more jobs.

For example "a PR workflow" could have multiple jobs but we now spawn multiple workflows per PR.

Merging purpose-alike workflows, gives a straightforward CI structure for maintainers.

[bernhste]

100% agree with "We may use workflows slightly more efficiently" (see my may CI issues from yesterday 😅😭). But I did not want to change anything which would introduce more uncertainty.

Please see also: #54. This one is about decouple the infrastructure so we can reuse it to test the agents (#57).

I was thinking making modules for iOS / Android environments and test apps and re-use them as much as possible.

Maybe force rebuilding AVD/iOS Simulators on every merge to main or once a month, but use cached snapshots otherwise because it takes a lot of time to fully build everything again for each simple commit. But I don't have much experience with caching or conditional builds in GitHub.

I'm all for a doing a dedicated issue / PR focusing on optimizing the CI. But I would do that after we merged #56.

[Diolor]

Yes any optimisation should after we have proper jobs! Also not targeting your work per-see @bernhste 🙂 🙏

Check OWASP/mastg#3691 (or even better review it 😄). It has use-case driven workflows (4 jobs per PR, 3 jobs on main branch) which under the hook reuse some scripts.

Regarding cache and incremental builds I also have only experience in GitLab but we can check here. But let's see first how much time our jobs we end up need per run.