All commands use IPFS Core API

[ghost]

Most of the "business logic" buried in the core/commands package should use the IPFS Core API. Once the basic commands are implements as a trial balloon, we wanna continue with most of the rest:

• block
• object
• files
• resolve
• name
• dns
• pin
• repo
• id
• bootstrap
• swarm
• dht
• ping
• config
• version

A few of the commands might not make much sense within the IPFS Core API, e.g. init, daemon, diag, update. This will be discussed in ipfs/interface-ipfs-core.

Dependencies:

• Gateway uses minimal IPFS Core API #2876 Gateway uses minimal IPFS Core API
  • for the basic Core API imeplementation
• Basic commands use IPFS Core API #3172 Basic commands use IPFS Core API
  • for the trial ballooning

[ghost]

Closing in favor of #4498