[feature/771] Github Actions: Env vars to configure docker images + new Alpine dockerfile for Crystal v1

[HashNuke]

Description

• Moves out image names to env vars in the Github Actions file
• Adds new Dockerfile for building the image for the Crystal v1 (this was AFAIK missing in the repo - so we don't have the source for the image being used for Crystal 0.35 in main branch)

If the PR looks good, apart from merging it, we should complete the following tasks to allow the next PR for Crystal v1 upgrade.

[Task] Push a new image for conformance/crystal

• Push conformance/crystal image to DockerHub

export IMAGE_NAME="conformance/crystal:1.0.0-alpine-r1" && \
docker build -t $IMAGE_NAME tools -f tools/crystal-alpine.dockerfile && \
docker push $IMAGE_NAME

[Task] Push new image for conformance/offline

• Push conformance/offline image to DockerHub

export IMAGE_NAME="conformance/offline:crystal-1.0.0-r1"

# Build the conformance/node image
docker build -t conformance/node:v1.21.1 tools/airgapped_kind/kind_node
docker save conformance/node:v1.21.1 > tools/airgapped_kind/kind_node/node.tar.gz

# Build the conformance/offline image (uses the tar file of the conformance/node image)
docker build -t $IMAGE_NAME tools/airgapped_kind
docker push $IMAGE_NAME

Issues:

Refs: #771

How has this been tested:

• Covered by existing integration testing
• Added integration testing to cover
• Verified all A/C passes
  • develop
  • master
  • tag/other branch
• Test environment
  • Shared Packet K8s cluster
  • New Packet K8s cluster
  • Kind cluster
• Have not tested

Types of changes:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Checklist:

Documentation

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• No updates required.

Code Review

• Does the test handle fatal exceptions, ie. rescue block

Issue

• Tasks in issue are checked off

[HashNuke]

For the docker images, the PR currently names the tags by crystal versions and allowing for new versions with r{n}. I just picked this naming convention - no strong preference. I'm open to any other naming convention.

[agentpoyo]

LGTM