fix(TripPlanner): Render time range correctly across midnight boundary

[joshlarson]

Scope

Asana Ticket: Trip Planner time display bug

Implementation

• Turns out, Cldr.Time.Interval.to_string!/4 has some strange behavior when the times given as the two ends of the range

iex> Cldr.Time.Interval.to_string(
...>   ~U[2026-02-09 10:00:43Z],
...>   ~U[2026-02-09 10:03:10Z],
...>   MyApp.Cldr,
...>   format: :medium
...> )
{:ok, "10:00 – 10:03 AM"}

iex> Cldr.Time.Interval.to_string(
...>   ~U[2026-02-09 10:00:43Z],
...>   ~U[2026-02-10 10:03:10Z],
...>   MyApp.Cldr,
...>   format: :medium
...> )
{:ok, "10:00:43 AM"}

• The fix is to strip the date info off of the time range (which I did in the helper), so that we're passing Time's in rather than DateTime's.
• (Bonus??) I went rogue a bit and added a +1 superscript when the trip crosses a day boundary.

Screenshots

This works in non-English too!

How to test

This is the trip shown in the screenshots above.

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1212887765217551