feat: modify /plan-journey so it returns bus polylines, /getAllRoutes & /getAllRideRoutes to return processed data

[jumpy-cat]

Description

Move the majority of bus route line processing into the backend so that more information in available during journey planning. Modify plan journey so that its bus legs contain polyline info. Refactor changed routes to use documented.

Type of Change

• New feature (feat)
• Bug fix (fix)
• Refactor / code improvement
• Dependency / build update
• Documentation
• Other (explain)

Related Issues

Backend Side of mbusdev/bluebus-flutter#98

Changes Made

• Flutter: n/a
• Backend (TypeScript):
  • new api/v4/ router for backwards incompatible changes
    • (WIP) contains new getAllMbusRoutes and getAllRideRoutes
  • the responses from bustime servers /getpatterns are now checked against zod schemas before being processed into BusRouteLines similar to those used in the frontend (but missing a few fields)
  • existing usages of routes / ride routes refactored to use processed bus route lines
  • getpredictions -> processPredictions -> (various usages) refactored to add type safety. Was trying to confirm if StopTime needed rt to be optional, turns out it does since the virtual origin/dest trips don't have a route
    • zod schema validation done (more strict than needed, might loosen if bustimes misbehave)
    • adjusted tests to look for new zod parse error instead of previous error message
• Firebase / Shared: n/a

Testing Done

Flutter:

• Tested on:
  • iOS Simulator
  • Android Emulator
  • Physical device

Screenshots / Demo (if UI or notification change)

Checklist

• Commit messages follow Conventional Commits
• PR title follows [type](scope): short description
• PR target branch is not main and is our current working update branch (e.g. maizebus2.1)
• No print() / debugPrint() / console.log() left in production code
• Secrets / keys not committed