Third sports-source provider: livetennisapi (point-level live tennis state)

[bensynapse]

Disclosure up front: I run the Live Tennis API (https://livetennisapi.com), so this is a vendor-authored proposal — judge accordingly.

src/lib/sports-source/providers.ts currently registers ['thesportsdb', 'pandascore'], and neither provider carries point-level live tennis state. For operators creating tennis markets, that means match cards can't show in-play state (set/game score, server, break points) and resolution has to lean on slower general-sports data. I'd like to propose livetennisapi as a third provider, following the file's existing extension points exactly:

• providers.ts: add 'livetennisapi' to SPORTS_SOURCE_PROVIDERS, a liveTennisApiKey field on SportsSourceProviderAvailability, a case in formatSportsSourceProviderLabel and getConfiguredSportsSourceProviders, and a tennis branch in filterSportsSourceProvidersByCategory (it's a sports-category provider, scoped to tennis).
• settings.ts: a sports_livetennisapi_api_key entry in the ai settings group, decrypted via the same decryptSetting path as sports_thesportsdb_api_key.
• Wiring in auto-selection.ts / search-query.ts, a fetch adapter for live scores + fixtures + players, a logo under public/images/logos/, and a settings docs page.

Plain words on tiers, since your operators already supply their own provider keys (PandaScore, TheSportsDB): live match state — score, server, break-point state, plus fixtures and player data — is on our free keyed tier (30 req/min, 100 req/day; fine for develop-and-test, not continuous fast polling). Market resolution needs completed-match results, which sit on our Basic tier at $9.99/mo. I'd rather state that here than have an operator discover it after wiring the provider in.

Free keys are self-serve at https://livetennisapi.com/subscribe/free and the API is documented at https://docs.livetennisapi.com — I'll gladly set up a key for any maintainer who wants to evaluate it. If the direction fits, I'll build the PR to your conventions; if a vendor-backed third provider isn't something you want in core, no hard feelings — say the word and I'll drop it.