Ideas: `versionGuard`, multiple instances of bitcore-lib

[braydonf]

Consolidating/moving issues related to versionGuard:

• Include more details in versionGuard message (Include more details in versionGuard message bitcore#1328)
• Issues with Electron (When using Electron, the symlinking strategy will still load bitcore-lib multiple times. #61)
• Remove versionGuard, or lower to warning (Remove include guards #21)
• bitcore-node related issue: Multiple instances of bitcore bitcore-node#308
• load library from global in case of conflict (Allow multiple instances of bitcore-lib with the same version #4)
• update bitcore modules to use bitcore as a peerDependency (update bitcore modules to use bitcore as a peerDependency bitcore#1232)

[fed-franz]

This "multiple instances of bitcore-lib" issue should really be avoided. It is extremely hard to solve and it prevents the development of new services.
And judging by the number of issues opened because of it, I think it should be given high priority.

[levino]

Please remove the includeGuard.