Support --json output on all CLI commands for nicer command pipelining

[rvagg]

Enforce this across all commands, come up with a pattern to provide output that's either nice stdout or JSON, perhaps a very basic template processing system that takes the same input and spits out the appropriate output.

[SgtPooki]

This will make using the github action (#49) much easier.

[SgtPooki]

FYI: gh-action will not depend on using json, we have too much UI in the action, so we'll likely keep using JS, but will simplify the #60 changes with #80

[SgtPooki]

@rvagg just wondering if you would be open to supporting an ndjson output with --ndjson so we can pipe out valid json as we get details. I'm looking into #157 now and was just thinking about how waiting until the very end is not ideal for all scenarios.

e.g. an add CLI operation could output things like:

{ "contentValidated": true }
{ "connectedToNetwork": true }
{ "paymentCapacityVerified": true }
{ "ipfsRootCid": "bafyfoo" }
{ "carCreated": { "fileSize": 1024, "blocks": 3 } }
{ "storageContext": { "dataSetId": 123, "providerId": 456 } }
{ "uploadProgressPercent": 10 }
{ "uploadProgressPercent": 60 }
{ "uploadProgressPercent": 100 }
{ "pieceAddedToDataSet": { "tx": "0x123", "details": { "pieceCid": "bafyfoo", "pieceId": 123 } } }
{ "ipniAnnounceSucceeded": "bafyfoo" }
{ "confirmedOnChain": true }

and someone could consume that with a simple npx filecoin-pin add ./dir --ndjson | jq -s 'reduce .[] as $item ({}; . * $item)' to collect it all:

{
  "contentValidated": true,
  "connectedToNetwork": true,
  "paymentCapacityVerified": true,
  "ipfsRootCid": "bafyfoo",
  "carCreated": {
    "fileSize": 1024,
    "blocks": 3
  },
  "storageContext": {
    "dataSetId": 123,
    "providerId": 456
  },
  "uploadProgressPercent": 100,
  "pieceAddedToDataSet": {
    "tx": "0x123",
    "details": {
      "pieceCid": "bafyfoo",
      "pieceId": 123
    }
  },
  "ipniAnnounceSucceeded": "bafyfoo",
  "confirmedOnChain": true
}

[rvagg]

yeah, that'd probably be fine, I think jq is always good with either nd or plain json and I imagine it to be one of the primary downstream uses of this output