WebsocketProvider - Error Handling

[nivida]

Description

I've compared the current errors with the errors we do throw in the refactored WebsocketProvider and adjusted those who would introduce a breaking change.

During the comparison of those did I notice that the old WebsocketProvider does have two different timeouts. The first place the old provider does check for a timeout is in the _parseResponse method and is per chunk and the other configurable timeout in _addResponseCallback is on a per request base. I will check that closer to be sure it won't break anything.

Type of change

• Error Handling

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 new warnings.
• Any dependent changes have been merged and published in downstream modules.
• I ran npm run dtslint with success and extended the tests and types if necessary.
• I ran npm run test:unit with success and extended the tests if necessary.
• I ran npm run build-all and tested the resulting file/'s from dist folder in a browser.
• I have updated the CHANGELOG.md file in the root folder.
• I have tested my code on the live network.

[coveralls]

Coverage increased (+0.5%) to 88.042% when pulling 3ca9b09 on pri/error-handling into 7b6a389 on provider-related-improvements.

[cgewecke]

Yes, makes sense and looks good! 👍