Fix automation exporter credential handling for Slack and Twilio

[TopProjectsCreator]

Motivation

• Generated exporter code for automation blocks used generic *_API_KEY assumptions and produced snippets that didn't match provider docs for Slack and Twilio.
• Align generated Python/Node snippets and environment variable guidance with the official webhook/SMS API patterns so exported pipelines work out-of-the-box.

Description

• Updated Python generator snippets in AutomationTemplatePane.tsx so Slack uses SLACK_WEBHOOK_URL with requests and Twilio uses TWILIO_ACCOUNT_SID + TWILIO_AUTH_TOKEN with the official messaging call and message/to/from fields.
• Updated Node.js generator snippets so Slack posts to incoming webhooks using node-fetch (with non-2xx checks) and Twilio authenticates with TWILIO_ACCOUNT_SID + TWILIO_AUTH_TOKEN and uses the expected message parameters.
• Adjusted the exporter credential discovery/validation logic so needsAuth emits the correct environment variable names and extra env var hints for Slack and Twilio instead of the generic *_API_KEY tokens.

Testing

• Ran npm run lint which completed successfully (existing unrelated warnings remain in the repo).
• Ran npm run test -- AutomationTemplatePane which found no matching test files (no unit tests were executed for that filter).

---

Codex Task