Rewrite Megaphone server using Actix framework

[data-sync-user]

Currently the megaphone server uses an older version of Rocket as it’s framework, which requires rust nightly. This was fine when it was originally created 6 years ago, but a lot of things changed, and now we would like to centralize to the actix framework.

Megaphone is in long maintenance mode, and this would be a reasonably significant effort, but would improve overall security and long term support for megaphone.

┆Issue is synchronized with this Jira Task

[jbuck]

@alexcottner and I were debugging why Telescope checks to megaphone were not working correctly, and we also came to the conclusion that autopush should talk directly to remote settings instead of rewriting a HTTP service to hold a single variable. Thoughts?

[data-sync-user]

➤ JR Conlin commented:

It’s certainly possible. I’d have to look into what megaphone is doing, the storage requirements, and how best to get rid of it. (Philip Jenvey was responsible for the initial version, IIRC, so he may have insight if this is viable or not. (Provided he remembers all the bits still.))

I can add a child task to look into replacing megaphone.