fix(web, isConnected): Return actual connection state even if network type is 'unknown'

[eVoloshchak]

Overview

Whenever connection type is 'unknown', library returns isConnected=false instead of actual connection state. Unknown network type does not necessarily mean that we have no internet connection. For instance, Electron apps and apps running on chromebooks with instant tethering enabled return 'unknown' network type even when connected to the internet.

Reasoning

We should return the correct connection state even for 'unknown' connection type

Test Plan

1. Launch app on chromebook with instant tethering enabled
2. Bind change event listeners to the NetworkInformation
3. Verify that isConnected property is present in state returned from the listener and that it indicates actual network state

Fixes #450

[mikehardy]

I worry about altering the isConnected type, as mentioned in the comment tagged on that line, this would be breaking and reverse an intentional change made earlier this year

[mikehardy]

just docs now as commented with specifics, then good to go

[mikehardy]

Looks excellent, CI checks then 🚀

[matt-oakes]

🎉 This PR is included in version 7.1.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀