chore(ci): when deploying compass web, deploy to all previous environments to make sure release version is consistent

[gribnoysup]

This patch changes compass-web deploy workflow to accoutn for some things we discussed during the demo of the new release:

• Now when selecting the environment for deploy, the workflow will release compass-web to all previous environments first. If any of those tasks fails, the release will stop
• I also changed the logic around which version will be released: instead of using current default (which would be the main HEAD), we resolve the latest dev release version. As the comment in the code mentions, this is actually more in sync with our release process and as @paula-stacho noticed, if someone merges to main just at the moment when you start the release, the main HEAD might actually point to a release that doesn't exist yet and the whole process will fail.

As mentioned, I went back and forth a bit about how to implement this, at the end I decided to keep some of the shell scripts right in the action jobs because moving them to dedicated scripts was making reading through the flow more confusing. I moved the latest release resolution to its own thing though because this one was the messiest in bash and needs to be reused in a couple of places. Tell me though if you think that those are too hard to read through

Code-wise I think it's ready for review, I tested all the parts separately and don't expect changes. Draft while I'm testing this with real GHA