Change Details

Previously there was an edge case: 1. Tunnelbroker socket state is `connected: true` and `isAuthorized: false` 2. After calling `setUnauthorizedDeviceID(false)` the state is `connected: true` and `isAuthorized: true`, but the connection is still opened using the unauthorized type 3. Next, the socket is closed and the state is `connected: false` and `isAuthorized: true` 4. After the authenticating socket is in state `connected: true` and `isAuthorized: true` As you can see - both 2 and 4 return the same result, but point 2 is not correct. This diff fixes this.

Previously there was an edge case: 1. Tunnelbroker socket state is `connected: true` and `isAuthorized: false` 2. After calling `setUnauthorizedDeviceID(false)` the state is `connected: true` and `isAuthorized: true`, but the connection is still opened using the unauthorized type 3. Next, the socket is closed and the state is `connected: false` and `isAuthorized: true` 4. After the authenticating socket is in state `connected: true` and `isAuthorized: true` As you can see - both 2 and 4 return the same result, but point 2 is not correct. This diff fixes this. This bug can cause issues described in [ENG-8385](https://linear.app/comm/issue/ENG-8385/qr-code-login-is-not-working-on-master)

Previously there was an edge case: 1. Tunnelbroker socket state is `connected: true` and `isAuthorized: false` 2. After calling `setUnauthorizedDeviceID(false)` the state is `connected: true` and `isAuthorized: true`, but the connection is still opened using the unauthorized type 3. Next, the socket is closed and the state is `connected: false` and `isAuthorized: true` 4. After the authenticating socket is in state `connected: true` and `isAuthorized: true` As you can see - both 2 and 4 return the same result, but point 2 is not correct. This diff fixes this. This bug can cause issues described in [ENG-8385](https://linear.app/comm/issue/ENG-8385/qr-code-login-is-not-working-on-master)