Co-authored-by: Marcin Rataj <lidel@lidel.org>

Co-authored-by: Marcin Rataj <lidel@lidel.org>

This ensures sharness tests are not broken when new version of
rb-pinning-service-api lands in master

- wip support for Pin.origins (commented out)
- safeguard against remote service changing remoteid during add with
  background=false
- change default output to follow commands like 'files stat'
- add bunch of TODOs for identified problems
- 'pin remote service add'
  - require three arguments
  - validate that URL is URL and starts with http
  - refactor relevant tests
  - add test for invalid URL (two cases: 404 and DNS)
- go mod tidy
- tests
  - 'pin remote ls'
    - switch --status to working notation, add TODO about supporting
      shorter form
    - removed 'sleep' from tests
      (we are testing 'pin remote', not the pinning service itself)
    - added test for inlined CID

- by default outputs two columns separated with tab, just like 'key
  list' does
- when --enc=json is passed, an object with RemoteServices array is
  returned (mirroring what 'key list' does)

This deduplicates code responsible for printing single PinStatus
response, and adds support for checking status based on RequestID
which is required by ipfs-webui integration.

Next step is to support more than one RequestID.

This adds support for checking status of multiple remote pins via single
command. should save a bunch of time in userland, including ipfs-webui

While at it, fixed some tests to be more reliable.
This is still WIP (pin remote rm seems to be still buggy)

added requestid to error messages, so user can then
inspect/resume/remove the queued pin request

latest version has a smaller image shich should speed up CI a bit

sidenote:
this version hides go-ipfs used by rb-pinning-service-api behind NAT,
removing port conflict on local env, and simulating (reverse) NAT setup
for data transfer

improve CLI ergonomics by supporting support bothi notations:
--status=a --status=b and --status=a,b
--cid=a --cid=b and --cid=a,b

This should protect us against GitHub or Docker changing the default IPs

- makes scrubing not fail when field missing

This still needs:
- config replace
- tests

We want the default to be blocking by default, so the behaviour on the
CLI is the same as the old local `pin add` and we can add `pin local
add` later that behaves the same.

Another argument is that we don't want to surprise user that the item is
not pinned when they dont read the output of `pin remote add` and assume
success as "pinned" and not "queued"

This switches the default to be blocking, just like the old 'pin add`
is. This will make future `pin local add` easier to add in
a backward-compatible manner.

Pinning Services return  only pinned objects by default, which may be
confusing. This adds explicit default and list of available options,
so users are not surprised when non-pinned (eg. queued) pins are ommited
from default output.

We already hide delegate list inb Text output in `pin remote ls`,
this aligns `pin remote add` output to do the same.

Delegates list is still returned when `--enc=json` is passed (or on HTTP
API)

this is in preparation for
ipfs-shipyard/rb-pinning-service-api#8

when that lands, we will leverage the fact that inlined CID can be
pinned instantly on the remote service

This adds --pin-count opt-in flag that returns number
of 'queued/pinning/pinned/failed' pins at remote service
or 'offline' if fetch of pin counts was not possible

JSON representation uses PinCount object (missing when 'offline')

Requires LsBatchSync from
ipfs/go-pinning-service-http-client#4

- basic sanitization for Pinning.RemoteServices
  - TODO: 'config replace' still needs a fix
- tests mostly green thanks to inlined CIDs
  - TODO: filtering by status may have a bug, needs a closer look