Fix non disposable daemon init/start and attach to running daemons

[hugomrdias]

This PR reworks daemon spawn options and handling of start/init, it also makes sure spawned daemons attach themselves to running daemons on the default/provided repo.

Ref: #304

Fixes #305
Fixes #276

[daviddias]

@hugomrdias I've changed the target of this branch to PR against my branch. Let's merge both and then merge to master.

[hugomrdias]

@diasdavid this was already rebased with master I would prefer to keep both PR separate. But if you want to merge them, we should rebase yours with master, merge this one with yours, make sure the example work and then merge it back to this one with fast-foward.

[daviddias]

#304 has now master rebased onto it.

[daviddias]

Fails a bunch of tests on the browser with the same error:

  1) non-disposable go daemon
       should attach to initialized and running node:
     Error: Error: Request has been terminated
Possible causes: the network is offline, Origin is not allowed by Access-Control-Allow-Origin, the page is being unloaded, etc.
    at request.post.send.end (webpack://ipfsdctl/src/factory-client.js:100 <- node_modules/aegir/src/config/karma-entry.js:344964:27)
    at Request.IpfsdCtl../node_modules/superagent/lib/client.js.Request.callback (webpack://ipfsdctl/node_modules/superagent/lib/client.js:611 <- node_modules/aegir/src/config/karma-entry.js:302263:3)
    at Request.IpfsdCtl../node_modules/superagent/lib/client.js.Request.crossDomainError (webpack://ipfsdctl/node_modules/superagent/lib/client.js:628 <- node_modules/aegir/src/config/karma-entry.js:302280:8)
    at XMLHttpRequest.xhr.onreadystatechange (webpack://ipfsdctl/node_modules/superagent/lib/client.js:703 <- node_modules/aegir/src/config/karma-entry.js:302355:19)

Tests failing are:

  non-disposable go daemon
    ✓ should fail when passing initOptions to a initialized repo (3ms)
    1) should attach to initialized and running node
    2) should attach to running node with manual start
    3) should not init and start
    4) should init and start
    5) should only init
    6) should only init manualy

  non-disposable js daemon
    ✓ should fail when passing initOptions to a initialized repo (2ms)
    7) should attach to initialized and running node
    8) should attach to running node with manual start
    9) should not init and start
    10) should init and start
    11) should only init
    12) should only init manualy

[daviddias]

needs all tests to pass

@hugomrdias wanna make the tests work on the browser as well?

[hugomrdias]

it works now 🔥 🔥
sorry for the big PR but the behaviour between the 3 impls was very different, on the bright side all 3 impls support non-disposable and auto attaching in node and browser.

Pls review again.

[hugomrdias]

CI only has a commitlint error squash will fix that and 2 Windows random errors.

[achingbrain]

Minor nit: we've required merge-options above, why not use it here instead of Object.assign?

[achingbrain]

Attaching to running daemons is a great feature, LGTM.

[daviddias]

@hugomrdias what's missing for this PR to land?

[daviddias]

@hugomrdias not necessary anymore?

[hugomrdias]

no 0.47.0 has all this and more