Handle brand-specific quirks (GM, Tesla, BMW) that break a generic Smartcar integration when read/command requests fail unexpectedly

Steps

1. For GM brands (Buick, Chevrolet, Cadillac, GMC), detect the VEHICLE_STATE - ASLEEP error after 3-4 days of inactivity and prompt for an ignition cycle rather than retrying indefinitely; throttle pings to at most once per 30 minutes to avoid UPSTREAM - RATE_LIMIT errors, noting OEM app usage counts against the same limit
2. For Tesla, expect REMOTE_ACCESS_DISABLED errors to sometimes take hours to clear after a user enables remote access — don't treat this as a permanent failure
3. Require Virtual Key setup for Tesla before attempting 3rd-party commands on Cybertruck, Model 3, Model Y, and 2021+ Model S/X — commands fail without it
4. For enterprise Tesla fleets, complete 'Tesla tenant' setup before onboarding customer vehicles, and expect that changing tenant configuration later forces re-authentication for all connected users
5. For BMW/MINI, route web-based Connect auth only within the EU (via the separate BMW Energy API integration); outside the EU, only the Android/iOS SDK auth flow is supported