Include time_text field in /meetings/{id}/ and /races/?date= endpoints

Hi team, First of all, thank you for providing such a comprehensive horse racing API. We understand that the individual race detail endpoint (/races/{id}/) exists specifically for in-depth race information like runners, odds, and full statistics. However, having time_text exclusively at that deep detail level presents a practical challenge when rendering meeting cards and schedule headers. When displaying an entire meeting header or race pills across multiple tracks, having to fetch every single race detail endpoint just to retrieve one display value (the official post time) is an unnecessarily heavy operation for rendering a simple header. Because start_time in the meeting list can sometimes differ from the official local post time, not having time_text at the meeting level prevents displaying accurate, real-world race times upfront on the meeting overview. Our suggestion: Could time_text (e.g., "16:20", "17:50") be included alongside start_time directly within the race summaries returned by /meetings/{id}/ and /races/?date=? Key benefits: 1. Accurate Overview Headers: Consumers can render track headers and race ribbons with official, real-world post times immediately, without visual delays or initial timing discrepancies. 2. Better Resource Use: Deep detail endpoints can be reserved for what they are actually meant for (loading horses, jockeys, form, and odds when a user actively clicks into a race), rather than being called in bulk across every race simply to read a time string. 3. Instant Reflection of Delays: If a track reschedules post times, the meeting header will reflect the adjustment right away. Thank you very much for considering this enhancement!