Deployment Process for Raphael Image

[ff-dh]

Now that the project has users, we should instrument a deployment process for the application that allows for rolling it back in case of a bad build. Currently we upload every image to Docker Hub tagged latest. I think the easiest approach would be to manually make more releases when we know the build is good or integrate something like ff-release (v2) to automatically build and upload whatever's on main. That way we have a latest image we can manually roll back to a working configuration if it's broken on the server. @andylolz, you usually write the actions workflows for this kind of thing, does that sound about right?