chore(upstream-docs): update watched-document baseline

[github-actions]

A watched upstream document moved, or a fetch failure changed its
count, so upstream-docs-state.json no longer describes what the
watcher sees. Merging this makes the new observation the baseline the
next run compares against.

Read the upstream-doc issues this run opened before merging: this
accepts the new bytes as normal, and on its own says nothing about
whether the registers a driver decodes by have moved.

The required checks do not start on their own here. A pull request
opened with GITHUB_TOKEN starts no workflow run, so this one arrives
with an empty status rollup. Close and reopen it to run them. The
validate run dispatched against the branch head is a verdict you can
read in the meantime -- GitHub does not count it toward the rollup.

Opened by the watch-upstream-docs workflow.

[miravoss26]

Reviewed. Automated watch-upstream-docs baseline update to upstream-docs-state.json — no driver code touched.

• Two easee_cloud-watched docs changed content (hash + length updated), each with its own tracking issue already opened: #144 (Easee charger observations) and #145 (Easee ongoing session API). Worth a human skim of those two issues to confirm the actual doc diff doesn't affect the easee_cloud driver's assumptions — this PR only accepts the new baseline, it doesn't assert the driver still matches it.
• Two new docs added to the watch list (teslamate_vehicle, vag_vehicle) — first-seen entries, nothing to compare yet.
• No CI ran, as the PR body correctly notes — GITHUB_TOKEN-opened PRs don't trigger workflows here; that's expected, not a red flag. mergeable: MERGEABLE.

Safe to merge from my read — the real follow-up is reading #144/#145, not this PR itself.