refactor: Inline <.itinerary_group /> component into TripPlannerResultsSection

[joshlarson]

No Asana ticket.

I think this addresses this concern raised in #2232, by bringing both of the phx-click="set_expanded_itinerary_index"'es into the same file where the resulting expanded_itinerary_index is actually used.

[anthonyshull]

Only thing is we should have a fallback for itinerary_panel that logs if it doesn't get pattern matched and returns some default.

[joshlarson]

@anthonyshull how does bb42934 look? IMO it doesn't look great, but also that scenario should never happen, so I don't think we need to make it look too pretty O_o

(Also, Sentry.capture_message for logging, or do we have a better way?)

[anthonyshull]

@anthonyshull how does bb42934 look? IMO it doesn't look great, but also that scenario should never happen, so I don't think we need to make it look too pretty O_o

Yeah, that looks good.

(Also, Sentry.capture_message for logging, or do we have a better way?)

Yeah, that's what we've been using. I think you can use the extra option instead of converting the assigns to a string:
https://hexdocs.pm/sentry/Sentry.html#capture_message/2-options