Only log read error when WebSocket connection was closed unexpectedly

[Dkamps18]

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Problem/Feature

Currently logs on any WebSocket read error, normal closures also return a read error as you can't read from closed connections. These "normal closure" errors being logged can be confusing to some users

Description of Changes:

• Only log read error when WebSocket connection was closed unexpectedly

Checklist

• My code follows the Contribution Guide
• I have self-reviewed the changes being requested
• I have made comments on pieces of code that may be difficult to understand for other editors
• I have updated the documentation (if applicable)