Resolve parity nodes invalid "eth_getBlockByNumber" JSONRPC call

[joshstevens19]

Description

If you send a transaction with a parity node web3 does not take into account that parity nodes can return the transaction receipt even if the transaction has not been mined. Unlike geth who return it once it has been mined. This causes a invalid JSONRPC call to "eth_getBlockByNumber" passing in a null block number causing the nodes to throw bad requests. This change just makes sure it does not call "eth_getBlockByNumber" until it has been mined.

Type of change

• Bug fix
• New feature
• Breaking change
• Enhancement

Checklist:

• I have selected the correct base branch.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no warnings.
• I have updated or added types for all modules I've changed
• Any dependent changes have been merged and published in downstream modules.
• I ran npm run test in the root folder with success and extended the tests if necessary.
• I ran npm run build in the root folder and tested it in the browser and with node.
• I ran npm run dtslint in the root folder and tested that all my types are correct
• I have tested my code on an ethereum test network.

[coveralls]

Coverage increased (+0.001%) to 95.953% when pulling 2b23d48 on joshstevens19:resolve-parity-get-block-by-block-number-error into 6961fa2 on ethereum:1.0.

[coveralls]

Coverage increased (+0.001%) to 95.953% when pulling 2b23d48 on joshstevens19:resolve-parity-get-block-by-block-number-error into 6961fa2 on ethereum:1.0.

[coveralls]

Coverage increased (+0.001%) to 95.953% when pulling 3f2b18d on joshstevens19:resolve-parity-get-block-by-block-number-error into 5683436 on ethereum:1.0.