With expired Github token an "refresh page or contact support" error appears

Impact

Users cannot create new Github connections if their tokens have expired. (There is a workaround that can be provided by contacting support@openfn.org, but we should do better than that!)

Reproduction

When a user's personal GitHub token has expired (like this)

%{
  "access_token" => "shh!",
  "expires_at" => "2026-03-24T18:09:32.334729Z", # i am expired!
  "expires_in" => 28800,
  "refresh_token" => "shh!",
  "refresh_token_expires_at" => "2026-09-24T10:09:32.334818Z",
  "refresh_token_expires_in" => 15897600,
  "scope" => "",
  "token_type" => "bearer"
}

And they try to set up a new GitHub Repo Connection they see this error:

They're stuck, and there's nothing they can do but contact support. OpenFn's support team then tells them to go here and disconnect from GitHub, then reconnect to GitHub:

There is an unhandled error (https://openfn.sentry.io/issues/7494763373/?alert_rule_id=11218001&alert_type=issue&environment=prod&notification_uuid=dd1ee600-7d28-47ed-9be3-572026e6b20b&project=6446500) when they click disconnect, but once the disconnection is done and the reconnect, they get a new token and everything works perfectly.

Possible Solutions:

1. (OK? ⭐ ) Tell them why Github connection creation is broken. With an "expired token" message they might be able to figure out how to fix it.
2. (Better? ⭐ ⭐ ) Tell them how to fix it.
3. (Best? ⭐ ⭐ ⭐ ) Give them a button on the page with the error to "refresh" their GitHub connection
4. (Bester?) [ add new ideas here ]

Version

v2.16.4 (1.5.83)

No file or test is named. Start with the GitHub Repo Connection creation flow and the disconnect/reconnect flow described in the reproduction, then trace how an expired token is handled; done means users receive a useful recovery path instead of the generic error and can create a connection successfully.