make lotus-miner net commands hit markets subsystem.

[raulk]

The libp2p host on the miner is now only started where the markets subsystem runs. This PR makes lotus-miner net commands hit the node where the markets subsystem is running.

Honestly, Net no longer belongs in the Common commands, nor should the endpoint be resolved through GetCommonAPI/GetAPI, but there is some larger untangling to do to tidy this up, and it's associated with pre-existing tech debt.

Choosing not to do it now, as there are other decisions to make first with regards to providing the optimal UX experience for miners, now and as we introduce more miner services.

---

Testing: unfortunately we don't have a decent framework/suite for CLI testing. All itests hit the JSON-RPC API or the native API. So I can't add a test for this. Instead, I performed manual testing and all looks good.

[raulk]

Before

$ lotus-miner net peers
ERROR: method not supported

After

$ lotus-miner net peers
12D3KooW..., [/ip4/1.2.3.4/tcp/1]
12D3KooW..., [/ip4/2.3.4.5/tcp/2]
12D3KooW..., [/ip4/3.4.5.6/tcp/3]
12D3KooW..., [/ip4/4.5.6.7/tcp/4]

Note how I don't need to use --call-on-markets.

[dirkmc]

Nice 👍

[magik6k]

We also need to add NetCmd to cmd/lotus, otherwise we'll lose net commands on the chain process

[raulk]

@magik6k cmd/lotus uses lcli.Commands, which already has lcli.NetCmd, that's why it's not a problem. The only thing using lcli.CommonCommands is actually cmd/lotus-miner. That's why I say that this part of the codebase needs a deeper refactor.

lotus/cli/cmd.go

Line 70 in 5f61664

var Commands = []*cli.Command{

[jennijuju]

Nice! thanks for this - would be really nice to get in v1.11.1.