A staging server for rdsys

We want to set up a staging server of rdsys, that will be automatically deployed on each commit from the CI. We'll need a new VM for it. Many things will be similar to polyanthium, but we might not need separation of services by users (it might be easier to deploy if we have everything in one user).

We will not need much disk space, CPU or RAM, whatever are the defaults you use now a days will be enough for us.

What we need there:

• an account that we can ssh automatically from the CI to setup everything. let's postpone this
• We'll also need everybody from anti-censorship to be able to sudo into that account.
• an email account that can send and receive emails over imap and smtp. Maybe gettor-tst@torproject.org?
• a web server with:
  • https://bridges-tst.torproject.org proxing to http://localhost:7200
  • https://bridges-tst.torproject.org/moat proxing to http://localhost:7500/moat
  • https://bridges-tst.torproject.org/status proxing to http://localhost:7100/status
• prometheus exporters to be exposed, I don't think we'll connect them to the prometheus server, but will be useful to be able to reach them for tests:
  • backend bridges-tst.torproject.org:7100/metrics
  • telegram bridges-tst.torproject.org:7600/metrics
  • gettor-distributor bridges-tst.torproject.org:7700/metrics
  • gettor-updater bridges-tst.torproject.org:7800/metrics

I don't have a strong opinion for port numbers, the domain names and the email address, I'm just putting some proposals here but I'm happy to adapt to what you think makes sense.