For context, Coder Desktop's networking starts & stops itself on device wake & sleep, respectively. Both of these events can be sent by the operating system even when the device lid is closed, or when the screen is completely off, in order to check for network events.

There's two problems with this right now:

1. The procedure onwake sets the system VPN state toreasserting. The operating system does not wait for areasserting state to end before it callssleep.
   We currently do not handle any form of queuing for these events, so if the tunnel is still starting up, thesleep call is effectively ignored.
   This makes it possible for the VPN to be enabled when the last call from the operating system wassleep. It's not super clear what issues this causes, if any, but it's something we should fix.

2. A newcoder-vpn.dylib can be downloaded, even if the user is not present to enter their password & un-quarantine it.
   If this happens, the networking functionality will fail with an error, and the developer will have to toggle it in settings once again.
   Ideally, this shouldn't happen. Users should be able to wake their laptop from sleep, and CoderVPN should be in (or entering) the same state they left it.
   We should either find a way to recover from this error (by using the previously downloadedcoder-vpn.dylib), or simply not start the download if the tunnel was started by a call towake, where the user might not be present.