Connect to services over dmsg by default

[0pcom]

We should deprecate the http endpoints for the services or leave them there for testing or fallback only or simply for viewing the data from the service over http.

A loosely-enforced requirement for rewards is that visors must be connected to dmsg.

It is loosely enforced because some visors lose connection to dmsg ; the only hard requirement is that the survey was fetched one time over dmsghttp.

If the survey or health cannot be actively fetched because the visor disconnected from dmsg, the reward address, etc, is pulled from a cached or backed-up copy of the survey.

This creates an uneven playing-field between users who are forced to use a dmsghttp-config because they are in china or another region where that config is the default and users who use a plain http config.

It also presents a challenge for uptime tracking as a valid uptime should include or not exceed the time a visor is connected to dmsg.

As stated, the requirement of an active connection to dmsg is not currently enforced beyond the fetching of the survey.