fix: WS connections do not honor disable-validation

[roderik]

I noticed that as soon as I configure a WS upstream, that the disable-validation option no longer works. This is especially annoying with some hosted WS providers that do not expose the net namespace.

I used the same logic as the RPC upstream uses.

probably fixes:

• Lots of net_peercount errors on Alchemy node #155
• 0.12 spawns huge amounts of logs for ws connections #152
• I don't think role: fallback is working correctly anymore #85

[codecov-commenter]

Codecov Report

Merging #159 (381b2d5) into master (87c1ea9) will decrease coverage by 0.02%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master     #159      +/-   ##
============================================
- Coverage     55.30%   55.28%   -0.03%     
- Complexity     1343     1344       +1     
============================================
  Files           190      190              
  Lines          7077     7082       +5     
  Branches        859      860       +1     
============================================
+ Hits           3914     3915       +1     
- Misses         2679     2684       +5     
+ Partials        484      483       -1     

Impacted Files	Coverage Δ
...y/dshackle/upstream/ethereum/EthereumWsUpstream.kt	0.00% <0.00%> (ø)
...tlin/io/emeraldpay/dshackle/rpc/TrackEthereumTx.kt	78.53% <0.00%> (+0.48%)	⬆️

---

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 87c1ea9...381b2d5. Read the comment docs.

[splix]

Thank you!