boostx stats: output agent version and retrieval protocols

[dirkmc]

Fixes #1271

Total Boost nodes: 17
Total Boost raw power: 20588664467750912
Total Boost quality adj power: 164240643386998784
Total Lotus Markets nodes: 40
Total SPs with minimum power:  3603
Total Indexer nodes: 43
Agent Versions:
  lotus-1.18.0+mainnet: 1
  lotus-1.18.2+mainnet: 1
  lotus-1.20.0+mainnet: 2
  lotus-1.20.0-rc1+mainnet: 2
  lotus-1.20.0-rc2+debug: 1
  lotus-1.20.0-rc2+mainnet: 8
  lotus-1.20.6+mainnet: 2
Retrieval Protocol Support:
  bitswap: 1
  libp2p: 17

UserAgent

Unfortunately it seems that the UserAgent is being set to the lotus version imported by boost (not boost's build version).

This is because we build the Host using lotus modules rather than building it from boost modules:

boost/node/builder.go

Line 232 in f3622c8

Override(new(lotus_lp2p.RawHost), lotus_lp2p.Host),

The lotus modules code sets the AgentVersion from the lotus build version:

	opts := []libp2p.Option{
		libp2p.Identity(pkey),
		libp2p.Peerstore(params.Peerstore),
		libp2p.NoListenAddrs,
		libp2p.Ping(true),
		libp2p.UserAgent("lotus-" + build.UserVersion()),
	}
	for _, o := range params.Opts {
		opts = append(opts, o...)
	}

	h, err := libp2p.New(opts...)

We can fix this by writing our own boost UserAgent libp2p option override. See PR #1305

[jacobheun]

Other than the agentversion comment the rest of this looks good.