Feat: sp locator task

[jcace]

closes #679 , adding a scheduled task to run the PeerPingManager and wire up to the Estuary API, retrieving SP list to ping.

In addition, the following refactors were performed:

• Update API V2 /storage-providers/ endpoint, fixing nil bug and make it use gothreads (was missed in fix: sp info endpoint - chain info always null #908 )
• Extract ToMultiAddress and ToMultiAddresses functions out of node.go and into utils, as they're being used in multiple places
• Extract the Shuttle code that makes HTTP requests into a separate file ShuttleHttpClient, reducing duplication
• Rename tracer in deal/check.go/checkContentDeals, was missed in Refactor: break up replication into smaller modules #897

[jcace]

Currently blocked from testing by #905 , will test and finish up once that is resolved.

[en0ma]

@jcace is this still in draft or you want us to review as is?

[jcace]

@en0ma not done yet, soon!

[jcace]

Here's an example response from the new Shuttle /storage-provider/list endpoint:

[
	{
		"address": "f010617",
		"latency": 33
	},
	{
		"address": "f0135078",
		"latency": 38
	},
	{
		"address": "f01886797",
		"latency": 42
	},
	{
		"address": "f08399",
		"latency": 43
	},
	{
		"address": "f058369",
		"latency": 68
	},
	{
		"address": "f09848",
		"latency": 72
	},
	{
		"address": "f02401",
		"latency": 94
	},
	{
		"address": "f022163",
		"latency": 202
	}
]

[10d9e]

Looks good @jcace

To be safe, I am dismissing this as this comment needs to be addressed or it will break prod if deployed #907 (comment)

[en0ma]

LGTM