Full reconnect on n/w path changes

[pblazej]

This is a high-level solution - without changing any logic for the reconnect itself 🤔

• .quick cannot recover from "no connectivity" state
• ConnectivityListenerDelegate was basically unused
• There's StartReconnectReason.networkSwitch, but do we need an explicit startReconnect() here?
  • it will be triggered anyway, either by .websocket or .transport, we'll just hit the same state twice (with an error)

At least 2 scenarios to reproduce:

• Use local server and disable wi-fi
• Use any server with ✈️ mode (this is more likely to fail)

I'm still not sure how much ConnectOptions (timeouts) affect this case, does it work based on a "happy configuration"?

[ilo-nanpa]

it seems like you haven't added any nanpa changeset files to this PR.

if this pull request includes changes to code, make sure to add a changeset, by writing a file to .nanpa/<unique-name>.kdl:

minor type="added" "Introduce frobnication algorithm"

refer to the manpage for more information.

[pblazej]

Closing for now, in favor of #664 and further improvements in this area.