Fix #1537 (Item 4): Add accessibility support for arrival badges

[Gitkbc]

I've implemented the accessibility issues for arrival badges (Item 4 of #1537).

Instead of TalkBack just reading out the tiny badge text, I updated the StarredStopsAdapter to generate a full sentence description—something like "Route 10, arriving in 5 minutes." I also silenced the HorizontalScrollView container so the screen reader doesn't get stuck on it, making it much smoother to swipe through the actual arrival times.

Tested with TalkBack on a physical device — before the fix it read "list", after the fix it correctly announces each badge.

[Gitkbc]

@aaronbrethorst Sir,

While testing this, I noticed that when a stop has multiple arrivals for the same route, TalkBack reads "Route 128, arriving in 8 minutes" then "Route 128, arriving in 33 minutes" — the repeated route name feels a bit redundant both visually and for screen reader users.

Would it be worth showing the route name once and labeling subsequent badges as "Bus 1", "Bus 2"? Also the TalkBack will be "Arriving: Route 128, Bus 1 in 6 minutes, followed by Bus 2 in 33 minutes." I've attached a quick hand-sketch of what I mean. If this sounds like a good enhancement, I’m happy to present a digital preview so we can see exactly how it looks before coding it. Happy to explore this as a follow-up if it sounds useful.