Allow web3 provider options for bitcore.config.js

[rlaace423]

There's web3 provider issue when rpc result is too big it fails to keep connection (especially WS provider)
For example,

• a lot of transactions (ex: ropsten 599275th block)
• a lot of trace_block

For this issue, we can pass Web3 constructor's options when initiate Web3.
I edited small amount of codes which can allow web3 can have options.
Now we can append options to Web3 like below.

FYI, here's my original issue #2735
And here's web3 issue about clientConfig web3/web3.js#1217 (comment)

Always, thank you @micahriggan :)

[micahriggan]

Thanks for this! Tricky one to find

[micahriggan]

Is the number 1073741824 based off of what you needed for the ropsten block to be processed, or can a smaller number be used?

If this is bytes, then that'd be a gig right?

[rlaace423]

Is the number 1073741824 based off of what you needed for the ropsten block to be processed, or can a smaller number be used?

If this is bytes, then that'd be a gig right?

That number is just for my test :) maxReceivedFrameSize and max ReceivedMessageSize are based off bytes.
Much smaller number can be used.

[micahriggan]

okay, great thanks!