fix(web): Confluence creds stale cache + configured badges on settings disclosures

[jstuart0]

Summary

• Bug A — stale Urql cache: Add requestPolicy: "network-only" to the useQuery(LIVING_WIKI_GLOBAL_SETTINGS_QUERY) call in wiki-settings-panel.tsx. The /settings/living-wiki page saves credentials via raw authFetch (no Urql mutation), so the document cache never gets invalidated. Without this change, a user who lands on a repo page before saving creds gets confluenceToken: null cached; returning after saving still gets the stale null from the cache, leaving the Confluence sink grayed out with "(credentials not configured)". network-only forces a fresh server fetch on every panel mount.

• Bug B — no configured-state indicator: Extend the Disclosure component in settings/living-wiki/page.tsx with an optional configured?: boolean prop. When true, renders a green "Configured" pill beside the label; when false, a muted "Not configured" pill. Applied to all four credential groups (GitHub, GitLab, Confluence, Notion) using the respective token field as the indicator. The disclosure does not auto-open on save — only the badge changes, giving the user instant confirmation that save worked without disrupting their scroll position.

Test plan

• cd web && npm run lint — clean (one pre-existing warning in ImproveLabelsButton.tsx only)
• cd web && npm run build — clean
• Settings page: with no creds set, all four disclosures show "Not configured" badge when collapsed. Enter and save GitHub token → badge changes to green "Configured" without expanding the disclosure.
• Repo wiki settings panel: set Confluence creds on the settings page → navigate immediately to a repo → Confluence sink is enabled (not grayed out), confirming no stale cache served.

🤖 Generated with Claude Code