Read Teslemetry sunroof state over parked Bluetooth

[Bre77]

Breaking change

Proposed change

Add a sleep-aware INFO scheduler to the BLE data manager and a sunroof cover
sourced from it. When the vehicle is BLE paired, the scheduler reads a single
closures_state() snapshot only while a command-opened link is up and the
vehicle reports itself awake (VCSEC) and parked (streamed gear P); it refreshes
at most every 60 seconds, extends the active window on user/charging/sentry
activity, and after 15 idle minutes disconnects and stays quiet with no
autonomous reconnect or wake. The sunroof is per-connection-generation local:
a link drop marks it unavailable with no stream or cloud fallback. The existing
sunroof-installed metadata gate is preserved.

This stacks on #979 (its base branch), part of the series moving cheapest-source
vehicle values onto the local Bluetooth link.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies a diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.