Set up a domain-fronted end point for wolpertinger

Censorship measurement platforms like OONI can request bridges to test from wolpertinger's REST API. Some platforms may be unable to talk to wolpertinger because it runs on bridges.torproject.org, which may be blocked. (This isn't an issue for OONI because it intends to proxy wolpertinger requests over its backend.)

We should set up a domain-fronted endpoint to fix this issue: In addition to a direct connection to bridges.torproject.org/wolpertinger, censorship measurement platforms should be able to use a domain front at ajax.aspnetcdn.com.

After reading legacy/trac#27469 (moved) and legacy/trac#16650 (moved), I believe that we need to configure another azure reflector, e.g., wolpertinger.azureedge.net, which is hooked up to https://bridges.torproject.org/wolpertinger/.