command: model remaining autonomy/autopilot domain and vehicle lighting fields

[Bre77]

Intent

• A cross-version protobuf diff (4.56 -> 4.58 app releases) surfaced a handful of fields this package hadn't modelled yet. Most of what it flagged - the FSD usage cluster on DriveState, autopilot entitlement on VehicleConfig, the multi-axle TPMS fields, Cybertruck side-storage closures, the ChargeLimitReason/HeadlampType_E/SeatTrimType enum additions, and the four new VehicleAction slots - turned out to already be modelled from the initial release's own app-4.58.6 baseline. This PR adds the genuine remainder:
  • UniversalMessage.Domain.DOMAIN_AUTOPILOT - a new routing domain value, wired and in active use (absent from older builds, present in the current one).
  • VCSEC.AutonomyCommand, wrapping a PullOverCommand trigger (empty body - remote "pull over" for a vehicle under autonomy), wired into UnsignedMessage field 66.
  • VehicleState.deck_lights_on / hazards_on - two plain booleans missing from an otherwise-complete lighting/status field set.
• Verified directly against teslamotors/vehicle-command and teslamotors/fleet-telemetry - none of these three are in Tesla's public repos yet. Publishing them anyway per the standing policy: this package tracks Tesla's real protobuf surface, not just the subset Tesla has open-sourced, and all three are real, wired fields observed in the current app rather than speculative additions.
• Held as app-only / not added: a commandcenter.Transport enum value and a ProxyCommandAction field - the commandcenter package isn't modelled in this repo at all, and the field itself has no recoverable name. Same reasoning for an unnamed ExteriorColor field addition - the containing message isn't modelled here either. Nothing worth guessing a name for.
• Regenerated both language packages; buf lint, buf breaking (against main), and the upstream coverage gate are all green.
• Adds a minor changeset (new enum value + new message/field additions = wire-compatible).