chore: update ipfs (#43)

* chore: update ipfs

The next ipfs release will be a dual ESM/CJS version which is presenting
some interesting challenges for all the different tools used here.

We also use the `ipfs` module everywhere when we could be using `ipfs-core`
instead - it's lighter and much quicker to install.  Really we should only
use `ipfs` when we need the CLI and the HTTP RPC API, though I'm a little
wary of the potential confusion for new users having two options introduces.

Author: achingbrain

package.json

@@ -13,7 +13,7 @@
     "test": "node tests/test.js"
   },
   "dependencies": {
-    "ipfs": "^0.58.1"
+    "ipfs": "^0.59.0"
   },
   "devDependencies": {
     "nanoid": "^3.1.23",

tests/test.js

@@ -16,7 +16,7 @@ async function startCliNode () {
     }
   }
 
-  const ipfs = require.resolve('ipfs/src/cli.js')
+  const ipfs = IPFS.path()
 
   await node.execa(ipfs, ['init'], opts)
   await node.execa(ipfs, ['config', 'Addresses.Swarm', '--json', JSON.stringify([`/ip4/0.0.0.0/tcp/0`, `/ip4/127.0.0.1/tcp/0/ws`])], opts)