Limit requested data for an access request

[WebSpider]

The "access-request"-type MQTT event is emitted for almost any action that takes place to/in the car. Opening doors, turning on lights, setting charge limits remotely all involve the "access-request" event.

Currently, we update the complete car. This is 8 API requests, consisting of:

• An updated view of the garage, with static information such as manufacturing date, model/year, engine, capabiltities and renders
• An updated view of the vehicle, with partially static information such as maintenance reports, your cardealership info
• The current vehicle status, with doors/locks status, renders and timestamp captured from the car
• The current vehicle driving range status, with information about fuel/charge, range
• The current AC status with current state, seat heating, charge port state, window heating, timers
• The current position
• The current charging information with charge speed, battery status, charge cable status and related
• The current health report from the vehicle with engine, tire, washer fluid, light, etc state

We don't do this on every event, since we throttle these requests for 30s, but still, that's a lot of information to refresh.

I propose we trim down the access-request events to the most interesting updates:

• The current vehicle status, with doors/locks status, renders and timestamp captured from the car
• The current position
• The current health report from the vehicle with engine, tire, washer fluid, light, etc state

Reason for this is that other, related, events already trigger other updates.

• If you switch on your AC, we will get an event for that and refresh the AC info.
• If you start charging, we will get an event for that and refresh the charging info
• Etc

[WebSpider]

With the amount of supported cars increasing, it is becoming increasingly impossible to limit requests. Let's just forget about this for now.