Build and publish container images

[mbaum0]

Closes: #150

This PR adds 2 new workflows

1. build-and-push-table-image: Whenever a new tag is created in the form of v*.*.*, this workflow will be triggered and container images will be built and pushed to ghcr with the provided version as a tag.
2. build-and-push-test-image: Runs on PRs that are opened on main. This is so we can test that the image build is successful with the changes, and also so one can test the actual image in deployment before merging.

Other changes:

• Add instructions to the readme for deployment using docker compose
• Updated the Dockerfile to support running consecutive builds on different architectures. This way we can publish arm64 and amd64 images in the same CI workflow.

@balzack I think you'll need to setup a GITHUB_TOKEN secret in the repository settings with write access to packages

Could someone look over the doc changes and let me know if they make sense?

[balzack]

From what I've read, the permissions list in the .yml file dictates the granted permissions. Let me know if there is somewhere else to enable package permission for the token.

This seems good to me, but containers aren't my strength, so hopefully someone else can take validate the PR, @lil5 ?

[lil5]

The test pr seems a bit overkill, it's faster to checkout the pr locally and try it than waiting for GitHub to build it, then copy over locally.

Someone even without any knowledge of git can use the GitHub instructions of their GitHub cli then run the dev docker compose.

Two commands:

gh pr checkout 1337
make dev-start

[lil5]

Shouldn't the args be placed first or doesn't that matter?

[lil5]

Why remove this?

[lil5]

Great improvements on the cache locations 👍

[lil5]

Would you be able to test this code on a personal public Fork? It a bit iffy to merge without testing the full process.

[lil5]

using sharing=locked could be an issue if 2 PRs are created at once