Infra setup for recovery and export frames

[r-n-o]

This PR has the basics:

• a new Dockerfile which installs and starts an nginx server, serving recovery and export frames on 2 different ports (8080, 8081)
• a new workflow to publish docker images to GHCR
• a new kustomize folder with configuration to define a service

Testing

• I have tested the Dockerfile locally, it works.
• I have published an image to ghcr
• I've also pulled that same image and ran it in a local k3d cluster

Next step: run this in our preprod cluster!

[james-callahan]

1. I don't think you actually need 2 server blocks here; you could just have two location blocks?
2. The container as written is non-reproducible; you might be able to get away with using a direct nginx upstream container? (it's no worse than the debian one...)

[r-n-o]

I don't think you actually need 2 server blocks here; you could just have two location blocks?

I need two server blocks if I want to serve on different ports (listen directive's only context is server: https://nginx.org/en/docs/http/ngx_http_core_module.html#listen)

The container as written is non-reproducible; you might be able to get away with using a direct nginx upstream container? (it's no worse than the debian one...)

Would switching to a direct nginx upstream solve the reproducibility problem, or is that a separate problem (as in: problem 1: container is not reproducible, problem 2: could simplify the dockerfile by using a direct upstream container).

Addressed comments