Refactor good-first-issue.js for consistency

[Vishal-ghorpade]

Hi maintainers 👋,

I noticed that when the GitHub API rate limit is exceeded, the CLI currently prints the full JSON error object. For new contributors, this can be overwhelming and makes the tool harder to use.

This PR improves the developer experience by:

• Catching the 403 rate‑limit error in bin/good-first-issue.js.
• Printing a concise, user‑friendly warning instead of raw JSON.
• Suggesting authentication with a personal access token for higher limits.

Before:

RequestError [HttpError]: API rate limit exceeded for ...
{ huge JSON dump }

After:

⚠️ GitHub API rate limit exceeded.
Tip: Authenticate with a personal access token to get a higher limit.
See: https://docs.github.com/en/rest/overview/resources-in-the-rest-api#rate-limiting

This change keeps the CLI output clean and beginner‑friendly, while still guiding users toward the right solution. I believe this small improvement makes the tool more approachable for first‑time contributors.

Looking forward to your feedback, and happy to adjust if you’d prefer different wording or formatting.

[bnb]

please fix your formatter.