Market data provider - Failed to fetch tickers for kucoin_perpetual and bitget_perpetual due to missing TickerSpec

[rapcmia]

Describe the bug

While running hummingbot-api and monitoring background market data collection, the server logs reported warning failures when fetching tickers for the kucoin_perpetual and bitget_perpetual connectors. The background ticker source expected a single bulk ticker endpoint for these connectors, but because no TickerSpec or spec alias was defined for them in services/ticker_sources.py, the price collector fell back to a pair-by-pair check. Since both connectors track hundreds of active pairs (674 pairs for KuCoin Perpetual and 789 pairs for Bitget Perpetual), the generic price collector aborted to prevent sending hundreds of individual HTTP requests in a single cycle.

2026-07-30 10:09:10,667 - services.ticker_sources - WARNING - Failed to fetch tickers for 'kucoin_perpetual': 'kucoin_perpetual' has no bulk ticker endpoint; pricing its 674 pairs would take one HTTP request each. Add a TickerSpec for this connector.
2026-07-30 10:09:10,668 - services.ticker_sources - WARNING - Failed to fetch tickers for 'bitget_perpetual': 'bitget_perpetual' has no bulk ticker endpoint; pricing its 789 pairs would take one HTTP request each. Add a TickerSpec for this connector.

The expected behavior is for hummingbot-api to collect prices in bulk for all supported exchange connectors without raising pricing warnings or aborting background ticker collection cycles. This issue was introduced when ticker collection was refactored in PR #199 to use declarative TickerSpec rules. Adding TickerSpec entries or alias declarations for kucoin_perpetual and bitget_perpetual (and bitget spot) will allow background ticker collection to complete cleanly.

Steps to reproduce bug

1. Enable or connect kucoin_perpetual or bitget_perpetual connectors.
2. Go to bots page
3. Observe background server logs from services.ticker_sources during ticker collection cycles.