Integrations need more information about how to get tokens

[neubig]

Currently when setting up the interface in OpenHands/agent-canvas, the user is asked for a bot token in slack, but there are no instruction in the UI about how to get this token. All supported integrations should have instruction links that are linked in the interface about how to get credentials.

[openhands-ai]

I'm on it! neubig can track my progress at all-hands.dev

[openhands-ai]

Summary of Work: Fix #279 — Integrations need more information about how to get tokens

Completeness Checklist

• Identified the root cause — All password-type credential fields in the integration catalog lacked helperText and documentation links, making it impossible for users to know how to obtain tokens/API keys when setting up integrations
• Added helperLink to the TypeScript type — Extended MarketplaceField in integrations/index.d.ts with helperLink?: string so UIs can render clickable documentation links
• Updated all 19 affected integration JSON files — Every password-type field now has both helperText (descriptive label) and helperLink (direct URL to credential creation page) for: airtable, apify, brave-search, clickhouse, elevenlabs, exa, figma, firecrawl, github, kagi, mongodb, neon, notion, obsidian, redis, resend, slack, supabase, tavily
• Added a regression test — test_credential_fields_have_helper_text_and_link in tests/test_catalogs.py enforces all future password fields must include both helperText and a valid https:// helperLink
• All 259 tests pass (including the new one)
• Sync check passes (sync_extensions.py --check reports "All extensions in sync")
• Branch pushed and PR opened — PR #281 on openhands/integration-credential-links

Conciseness

All changes are directly relevant to the issue. No extraneous modifications were made — every file touched either adds credential documentation to an affected integration field, extends the TypeScript type to support it, or adds a test to enforce it going forward.