pin: follow async pinner changes, use directly CoreApi.Pin.Verify

[MichaelMure]

This PR follow the changes in the Pinner to make listing recursive and direct pins asynchronous, which in turns allow pin/ls to build and emit results without having to wait anything, or accumulate too much in memory.

Note: there is a tradeoff for pin/ls?type=all:

• keep the recursive pins in memory (which I chose)
• ask the pinner twice for the recursive pins, and limit memory usage

Additionally, I improved CoreApi.Pin.Verify so that it can be used in the pin/verify command, instead or re-implementing everything.

Depends on:

• add Range for easier iteration Jorropo/channel#3
• pin: follow async pinner changes: improve Pin.Verify to support kubo needs interface-go-ipfs-core#109
• change the Pinner interface to have async pin listing go-ipfs-pinner#24
• Update to pinner having async pin listing go-ipfs-provider#48