[CI] Release artifacts job: binaries and containers

[okdas]

Summary

Provides binaries for releases and production-ready container images.

Issue

• [Infra] Binaries & builds for every actor #495

Type of change

Select one or more:

• New feature, functionality or library
• Bug fix
• Code health or cleanup
• Documentation
• Other (specify)

Testing

Documentation changes (only if making doc changes)

• make docusaurus_start; only needed if you make doc changes

Local Testing (only if making code changes)

• Unit Tests: make go_develop_and_test
• LocalNet E2E Tests: make test_e2e
• See quickstart guide for instructions

PR Testing (only if making code changes)

• DevNet E2E Tests: Add the devnet-test-e2e label to the PR.
  • THIS IS VERY EXPENSIVE, so only do it after all the reviews are complete.
  • Optionally run make trigger_ci if you want to re-trigger tests without any code changes
  • If tests fail, try re-running failed tests only using the GitHub UI as shown here

Sanity Checklist

• I have tested my changes using the available tooling
• I have commented my code
• I have performed a self-review of my own code; both comments & source code
• I create and reference any new tickets, if applicable
• I have left TODOs throughout the codebase, if applicable

[github-actions]

The image is going to be pushed after the next commit. You can use make trigger_ci to push an empty commit. If you also want to run an E2E test, please add devnet-test-e2e label.

[github-actions]

The CI will now also run the e2e tests on devnet, which increases the time it takes to complete all CI checks. If you just created a pull request, you might need to push another commit to produce a container image DevNet can utilize to spin up infrastructure. You can use make trigger_ci to push an empty commit.

[okdas]

I've tested this on the push trigger, but we don't have a good way to test the release creation from tag. Let's create the first tag after this is merged to test this CI job fully.

[okdas]

@Olshansk Upgrade to 1.22 was important for integration with the heighliner. I put the integration on pause, but I kept the upgraded version since I don't see any reason not to — Golang has great backwards compatibility and all tests seem to pass fine.

[Olshansk]

Just one non-blocking question!

[Olshansk]

Why is the poktrolld binary the entrpoint?

[okdas]

Why is the poktrolld binary the entrpoint?

glad you asked.

It allows to easy set up a shell alias to use poktrolld from docker without installing the binary on the machine. I'll showcase this in the docs.

[Olshansk]

#PUC

# poktrolld is the entrypoint to allow easily setting up a shell alias to use poktrolld from docker without installing the binary on the machine. I'll showcase this in the docs.
ENTRYPOINT ["poktrolld"]

[Olshansk]

@okdas ☝️