🚀 Feature: Fail setup more gracefully if the user isn't logged into gh

[JoshuaKGoldberg]

Bug Report Checklist

• I have tried restarting my IDE and the issue persists.
• I have pulled the latest main branch of the repository.
• I have searched for related issues and found none that matched my issue.

Overview

Forking from #398: if the user isn't authenticated in gh when they log in, they get a rather obscure error message with lots of noise trying to run pnpm run setup.

gh auth logout
pnpm run setup

◇  ❌ Error fetching gh auth status.
│
└  Looks like there was a problem. Correct it and try again? 😕


Error: Could not fetch github auth token. 
    at withSpinner (file:///Users/josh/repos/testing-private-repo/script/setup.js:166:10)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async file:///Users/josh/repos/testing-private-repo/script/setup.js:390:3 {
  [cause]: Error: Command failed with exit code 1: gh auth status
  You are not logged into any GitHub hosts. Run gh auth login to authenticate.
      at makeError (file:///Users/josh/repos/testing-private-repo/node_modules/.pnpm/[email protected]/node_modules/execa/lib/error.js:59:11)
      at handlePromise (file:///Users/josh/repos/testing-private-repo/node_modules/.pnpm/[email protected]/node_modules/execa/index.js:124:26)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async withSpinner.startText (file:///Users/josh/repos/testing-private-repo/script/setup.js:392:5)
      at async withSpinner (file:///Users/josh/repos/testing-private-repo/script/setup.js:160:4)
      at async file:///Users/josh/repos/testing-private-repo/script/setup.js:390:3 {
    shortMessage: 'Command failed with exit code 1: gh auth status',
    command: 'gh auth status',
    escapedCommand: 'gh auth status',
    exitCode: 1,
    signal: undefined,
    signalDescription: undefined,
    stdout: '',
    stderr: 'You are not logged into any GitHub hosts. Run gh auth login to authenticate.',
    failed: true,
    timedOut: false,
    isCanceled: false,
    killed: false
  }
}

...so much noise!

Instead, let's give them a more tailored error message. How about something like...

Error: Could not fetch github auth token. You are not logged into any GitHub hosts. Run gh auth login to authenticate.

(that's just a starting suggestion I haven't put much thought into - please improve it if you have any ideas!)

Additional Info

No response