ci: reorganise workflows (second try)

[0x009922]

Changes

• Rename files and workflows, no I2::Tests::Dev::PR nonsence anymore
• Merge most jobs into the primary ci.yaml that runs for all PRs and pushes to main
• Separate and parallelize jobs
• Use Rust cache wherever possible (and it could be improved further)
• Separate Docker Compose tests from pytests.
  • Run Docker Compose tests only when defaults changed (i.e. docker compose files). This job is heavy and bulky.
  • Pytests do not need docker compose. We have a great test_env.py which does the same and much faster.
• In Dockerfile, build only used binaries (irohad, iroha, kagami)

Result: main CI runs 16 minutes instead of 42 minutes.

Closes #5398

Postponed

• Re-enable SonarQube CI job #5403

---

Try 1: #5125

[0x009922]

It mostly works quite well!

CI completes in 16 minutes (when cache hits), which most checks parallelised as much as possible.

Need to fix SonarQube job (waiting for assistance of @BAStos525). Or maybe remove it entirely.

Also, for some reason pytests sometimes start on Amazon Linux and not on Ubuntu, which causes Python installation job to fail.

Things to improve:

• No clippy report for SonarQube
• Improve Rust caches further, specifically of wasm builds but maybe not only
• Add cache for Pytests
• Figure out why Pytests' CLI tests are so slow, they don't need to be this way (maybe just set a faster block commit time in test_env.py)

[0x009922]

For reference: currently the main workflow takes around 42 minutes!

https://github.com/hyperledger-iroha/iroha/actions/runs/14396113296

[aoyako]

Also, for some reason pytests sometimes start on Amazon Linux and not on Ubuntu, which causes Python installation job to fail.

Are there any error logs showing the issue?

[0x009922]

Are there any error logs showing the issue?

@aoyako Logs are no longer available: https://github.com/hyperledger-iroha/iroha/actions/runs/14530346551?pr=5399

[0x009922]

Changes:

• Do not run PR jobs (tests) on push to main; only in PRs
• Return publishing of iroha:dev image (publish_dev.yml). Only publish the image, without artifacts containing binaries and schema
  • Why no artifacts: first, packaging binaries is pointless as they are target-specific. If they are built in a docker image doesn't mean they will execute by themselves everywhere. As for schema, it is already committed in git. If needed - we can publish. What is actually useful is publishing of built WASMs, but they are already built as another artifact in the same job.
• Remove publish_nightly.yml manual job (unused as it seems)

[0x009922]

@aoyako @BAStos525 it happened again: pytests ran on Amazon Linux despite runs-on: ubuntu-latest.

https://github.com/hyperledger-iroha/iroha/actions/runs/14746025718/job/41393653249?pr=5399

[0x009922]

@BAStos525 Tried to run SonarQube job again - failed.

https://github.com/hyperledger-iroha/iroha/actions/runs/14746025718/job/41394151093

[0x009922]

For reference - publish_dev.yml worked as expected: iroha:dev

https://github.com/hyperledger-iroha/iroha/actions/runs/14788689301