Improve Error Handling on Failed Trip Booking

Currently, when a user tries to book a trip and the backend request fails (due to network issues, server errors, or invalid data), the UI does not provide clear feedback. This can confuse users and make it hard to understand if the booking was successful or not.

Expected Behavior:
If a booking fails, the user should see a clear error message indicating what went wrong (e.g., "Booking failed. Please try again later."). This should help guide the user’s next steps and improve trust in the platform.

Proposed Solution:
Improve the error handling mechanism in the frontend to gracefully catch API failures and display relevant messages to the user.

Benefits:
Enhances user experience by providing feedback in case of failure.
Makes the app feel more professional and complete.
Helps users retry or take appropriate action when something goes wrong.

No file or test is named in the issue. Start by tracing the frontend trip-booking flow and the backend request it uses, then identify how network, server, and invalid-data failures are handled. Done means failed bookings show a clear, relevant message that helps users understand whether to retry.

Written by the indexing model from the issue text.