Feature/tsp 976 update triggers docs

[jordanc-relevanceai]

Summary
This PR restructures and cleans up the Agent Trigger documentation to make it clearer, more consistent, and easier to navigate.

What changed:

• Triggers overview page (triggers.mdx): Slimmed down to a hub page with setup steps, trigger type cards linking to sub-pages, a “Choosing the right Trigger” comparison table, and general FAQs
• Scheduled Triggers (scheduled-triggers.mdx): Extracted from the parent triggers page into its own doc. Consolidated redundant “Why Use X” and “Making the Most of X” sections into a single intro. Covers recurring schedules (including cron expressions) and scheduled messages
• SDK & API Triggers (sdk-and-api-triggers.mdx): Merged the separate API and SDK pages into one doc, with SDK positioned first as the recommended approach. Includes full code examples for cURL, JS, and Python
• Webhook Triggers (custom-webhook.mdx): Rewrote to cut the fluff — removed “key features” that just restated how webhooks work and folded the useful config details (message templates, thread ID mapping, deduping) into the setup steps
• Tools as Triggers (tools-as-triggers.mdx): Removed the beta tag and disclaimer (feature has been live since June 2025). Added full setup walkthrough, deduping explanation, use cases, and FAQ about static inputs
• Integration Triggers (integrations.mdx): Restored as its own page covering 1,000+ integrations, premium triggers, and external triggers like Zapier
• Sidebar restructure: Renamed “Agent Triggers” folder to “Trigger Types” in the nav. Cleaned up the hierarchy so it reads clearly under the Agents section
• Deleted pages: Removed standalone Zapier page (now mentioned as an external trigger in the integrations doc) and separate SDK/API pages (merged into one)
• Consistency pass: Sentence case headings across all edited docs, standardised FAQ sections with accordion format, proper capitalisation for product terms (Agent, Triggers, Tools)
  Redirects: Added redirects for deleted pages so existing links don’t break

Why:
The trigger docs had grown organically — duplicate content between pages, a Zapier doc that was a copy-paste of the webhook doc, a Tools as Triggers page sitting in beta with one paragraph for 9 months, and inconsistent formatting throughout. This brings it all into a structure where each trigger type has a focused page and the overview actually helps users find the right one.

[linear]

TSP-976 Update Webhook & Zapier Trigger docs to be more relevant

[jordanc-relevanceai]

The old standalone Zapier page was a direct copy of the webhook doc with
no Zapier-specific content. Since Zapier setup is managed entirely within
Zapier's platform, it shouldn't need its own doc — just a mention as a
trigger type. Added under "Types of Triggers" in the Workforce triggers
page.

[alexrelevanceai]

yallah