Handle Smartcar API errors by type, distinguishing vehicle-state, permission, compatibility, and rate-limit errors instead of treating all failures the same way

Steps

1. Parse the type field on Smartcar error responses rather than relying only on the HTTP status code
2. Treat vehicle-state errors, such as a request blocked because the vehicle is currently charging or in motion, as retryable once the vehicle's state changes
3. Treat permission errors as a signal to prompt the user to reauthenticate or reauthorize scopes, using any resolution guidance included in the error payload
4. Treat a vehicle-not-capable compatibility error as terminal for that vehicle and stop retrying the same request
5. Back off and retry with delay when you receive a rate-limit error, keeping in mind per-vehicle brand rate limits are separate from your application-level Smartcar API limit