Migrate CI from CircleCI to GitHub Actions

[galargh]

User Story

GitHub Actions provides Developer Experience better suited for Lotus development team going forward.

Acceptance Criteria

• The p50 and p95 success rate of the new GitHub Actions workflows is the same or higher than their CircleCI counterparts
• The p50 and p95 execution time of the new GitHub Actions workflows is the same or smaller than their CircleCI counterparts (*p90 is worse for the Test workflow but it is due to an outlier caused by an issue with self-hosted runners that is being addressed)

Deliverables (GitHub Actions workflows)

Beta Give feedback

1. docs-check
2. gen-check
3. gofmt
4. lint-all
5. mod-tidy-check
6. test
7. test-conformance
8. test-itest-*
9. test-unit-*
10. docker-build
11. docker-push
12. release

Technical Breakdown

Tasks

Beta Give feedback

1. Create GitHub Actions jobs performing checks and generation (docs-check, gen-check, gofmt, lint-all, mod-tidy-check)
2. Provision self-hosted runners (large) for use in lotus (to accommodate expected high parallelism demands)
3. Create GitHub Actions jobs executing tests (test, test-conformance)
4. Create GitHub Actions jobs executing tests that require high parallelism (test-itest-, test-unit-)
5. Create GitHub Actions jobs executing docker builds (docker build, docker push)
6. Create GitHub Actions jobs performing release (release (dry), release)
7. Gather and compare CI stats for CircleCI job runs and their GitHub Actions counterparts*
8. Decommission CircleCI jobs after 1-2 weeks of stable execution of GitHub Actions counterparts*
9. Update lotus-priv clone

Testing

Beta Give feedback

1. Run the new GitHub Actions workflows in shadow mode for 1-2 weeks
2. Gather success rate and execution time metrics for both the CircleCI and GitHub Actions workflows
3. Compare and prepare a report

[Stebalien]

Any idea what caused the apt locking issue in https://github.com/filecoin-project/lotus/actions/runs/8529890853/job/23366624530?pr=11808?

[galargh]

Any idea what caused the apt locking issue in https://github.com/filecoin-project/lotus/actions/runs/8529890853/job/23366624530?pr=11808?

I have seen that before caused by ubuntu auto-updates but we disabled them since then. I propose we add extra logging to see what process is holding up the lock in case it happens in lotus again - #11815 Maybe bet would be that there is another scheduled process that is causing this.

[Stebalien]

Any idea why test runs like a40cced are showing up as failed? I assume they're just getting cancelled because we're merging something else to master, unless something else is cancelling them.

[galargh]

Any idea why test runs like a40cced are showing up as failed? I assume they're just getting cancelled because we're merging something else to master, unless something else is cancelling them.

That's exactly it. We can disable this with - #11842. Cancelling in progress runs is quite useful in the PRs, but we can do without it in other cases.