RPC providers - Chainstack is missing even though Gateway already exposes it

[rapcmia]

Describe the bug

While checking Condor gateway configuration, the issue showed up in the Telegram RPC Providers flow. Gateway already supports Chainstack as an available RPC provider, and the gateway routes and schemas show that it is part of the supported configuration. But in Condor Telegram, Chainstack does not appear in the RPC Providers menu, so users cannot configure or activate it from

This looks like a UI or handler mismatch rather than a backend support problem. The Condor route checks on port 8088 were available, and the Gateway-side schema already includes Chainstack for supported chains, but the Condor Telegram handler still appears to use a shorter hardcoded provider list. The gateway routes are already showing Chainstack as available, but Condor has not exposed it in Telegram.

---

WA: Use the custom_url to add chainstack node url

Steps to reproduce

1. Open Condor and go to /gateway
2. Open the RPC Providers menu.
3. Compare the listed providers with the Gateway-supported RPC provider options and schemas.
4. Notice that Chainstack is supported by Gateway but is not shown in the Condor Telegram RPC Providers menu.

Attach required files

No response