docs(integrations): fix GitHub personal-token instructions to not ask for a password

[fishmanalex]

Summary

• docs/integrations/providers/github/index.md, "Personal token" section, said: "Provide username and password."
• GitHub has not accepted account passwords for this kind of integration since 2021, and — confirmed against the actual wizard screenshot (wz_step2_token.png) — the real dialog has a single "Personal token" field, no username field at all, same pattern as GitLab's equivalent step.
• Every other token-based provider page in this docs set says "paste the generated token" with no username field either.

Changes

• Updated the instruction to: "Paste the personal access token you just generated." (matches the screenshot and the phrasing convention used elsewhere in this docs set)

Note: an earlier commit on this branch fixed the "password" wording but incorrectly added a username field that doesn't exist in the actual UI. That was caught during a re-verification pass and corrected in the second commit — the diff now reflects the final, screenshot-verified wording.

Test plan

• npx cspell on the changed file — 0 issues
• Verified against the actual wz_step2_token.png screenshot that the wizard step has only a token field
• Cross-checked wording convention against GitLab, Bitbucket, and other token-based provider pages

🤖 Generated with Claude Code

https://claude.ai/code/session_01QnXDhVitCVmMNafPRvKUat

[krassx]

Confirmed both ways. I opened wz_step2_token.png — the dialog is titled "GITHUB: PROVIDE TOKEN — STEP 2/4" and has exactly one field, labeled "Personal token", with the hint "You can obtain personal API token here: https://github.com/settings/tokens/new". No username field, no password field.

The server agrees — appserver/code/components/shared/integrator/modules/github/index.js:33-34 consumes a token and nothing else:

} else if (auth.mode === 'token') {
    clientOptions.auth = auth.token.access_token;

The self-correction called out in the description was the right instinct — the intermediate "username + token" wording would have been wrong too. Final wording matches both the screenshot and the convention on the other token-based provider pages. LGTM.

🤖 Generated with Claude Code

[krassx]

Validated against source (see review comment above). Approving.