Fix: WebSocket in the "Aborted" state cannot be closed.

[ricardo-salgado-tekever]

WebSocket connection which are aborted for some reason - client drop, ou load balancer drop - the call to GraphQL.Server.Transports.WebSockets.WebSocketReaderPipeline.Complete will throw an Exception:
"System.Net.WebSockets.WebSocketException (%d): The WebSocket is in an invalid state ('Aborted') for this operation. Valid states are: 'Open, CloseReceived, CloseSent'"

Aborted connection therefore should not be "closed", as it is already closed.

[sungam3r]

@ricardo-salgado-tekever Looks reasonable. Please bump version in Directory.Build.props to 5.0.2 and I will publish a new release.

[codecov-commenter]

Codecov Report

Merging #561 (6561c4d) into master (2ab8faa) will decrease coverage by 0.07%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #561      +/-   ##
==========================================
- Coverage   54.70%   54.63%   -0.08%     
==========================================
  Files          63       63              
  Lines        1497     1499       +2     
  Branches      151      151              
==========================================
  Hits          819      819              
- Misses        625      627       +2     
  Partials       53       53              

Impacted Files	Coverage Δ
...ubscriptions.WebSockets/WebSocketReaderPipeline.cs	0.00% <0.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2ab8faa...6561c4d. Read the comment docs.

[ricardo-salgado-tekever]

@ricardo-salgado-tekever Looks reasonable. Please bump version in Directory.Build.props to 5.0.2 and I will publish a new release.

Done!