Use bitcore-lib as a peerDependency

[CaptEmulation]

One wrinkle to using the bitcore stack is the obvious need to have a singleton bitcore-lib. The bitcoin-lib package hosts the bitcoind library and there are good reasons to not wanting to have multiple bitcoind instances running on the same machine.

However, I am not a fan of the runtime check and would rather have all packages be declaring bitcoin-lib in peerDependencies. This way the enclosing package can specify whatever version of bitcoin-lib it wants and npm will inform user if there is an unmet dependency at install time rather than run time.

I have a working example of bitcore-lib running as a peerDependency at bitcore-docker-build which is also running testnet at bitcore.soapbubble.online/insight
:

[CaptEmulation]

Also depends on:

• Use bitcore-lib as a peerDependency bitcore-node#500
• Use bitcore-lib as a peerDependency bitcore-p2p#92
• Use bitcore-lib as a peerDependency insight-api#501
• Use bitcore-lib as a peerDependency bitcore-message#27

[coveralls]

Coverage remained the same at 83.189% when pulling 38bb8f2 on CaptEmulation:bitcore-lib-as-peer-dependency into 4f7ddac on bitpay:master.

[coveralls]

Coverage remained the same at 83.189% when pulling 3374096 on CaptEmulation:bitcore-lib-as-peer-dependency into 4f7ddac on bitpay:master.

[matiu]

I think this is not longer needed in current npm. thanks!