MacOS: Inconsistent behaviour when key is revoked while machine is asleep.

### What is the issue?

If my Mac is asleep or locked while a key is revoked, the UI does not register that I'm no longer connected to the tailnet.

`/Applications/Tailscale.app/Contents/MacOS/Tailscale status` and the GUI menu act normally as if it were still connected, but all connections fail. The `status` output updates to `active` when I try to ping, but the pings time out.

I can select an exit node, which appears to work but all internet connectivity fails.

Turning Tailscale off and on with the toggle in the UI keeps it in this state. I have to switch accounts and back to get it to acknowledge I need to log in, or quit and relaunch Tailscale

### Steps to reproduce

Put Mac to sleep, remove the device from the Machines tab of the Admin Console. Wake the Mac up.

### Are there any recent changes that introduced the issue?

_No response_

### OS

macOS

### OS version

13.3.1

### Tailscale version

1.38.4 and 1.40.0

### Other software

_No response_

### Bug report

BUG-069d04b0850a27ab6ea92dd7da00efdfdf7b6b5018ca0785b18af0db1d3cd542-20230508155822Z-645e8a255a1ba82a

Start by reproducing the macOS sleep-and-revocation sequence, then compare the GUI menu with `/Applications/Tailscale.app/Contents/MacOS/Tailscale status` after wake. Done means the client recognizes that the key was revoked, updates its connection state, and restores connectivity or prompts for login without switching accounts or relaunching.

Written by the indexing model from the issue text.