Webhooks which call Edge functions should be configured via config.toml

Here’s a structured and ready-to-post GitHub Feature Request: ⸻ 🚀 Feature Request: Config-Based Webhook Management for Edge Functions Summary Currently, database webhooks in Supabase must be created either: • Manually via Supabase Studio, or • Through SQL migration files This causes security and configuration management issues, especially when authentication tokens are required. I propose enabling webhook configuration via the config.toml file, similar to other Supabase resources, with automatic provisioning during GitHub Actions or local CLI deploys. ⸻ ❗ Current Problems 1. Token Exposure in Migration Files When creating webhooks through migrations, any required token (e.g. Bearer token) must be embedded in SQL. This introduces security risks: • Tokens are stored in version control. • Token rotation becomes difficult. • Secrets management becomes inconsistent. ⸻ 2. URL Cannot Be Managed via Environment Webhook URLs are hardcoded in …