v0.2.0 — Weber Connect

Renames the integration to Weber Connect, gives it a proper icon, and makes a
retired refresh token recoverable from the UI.

Added

• Brand icon and logo — shipped in custom_components/weber_june/brand/, so
  Home Assistant serves them locally; no home-assistant/brands PR needed.
• Reauth flow — the cloud can retire a refresh token. When that happens the
  entry now asks for a new one instead of retrying forever, and the device, its
  entities and their history are kept.
• Appliance model and serial from the cloud — device name, model, model id and
  serial number are read from GET /2/devices/{companionId}/associated instead of
  being hardcoded. Optional: leave Companion id empty and generic info is used.
• Reconfigure step — an existing entry can gain a companion id without being
  removed and re-added.
• Diagnostics — dumps the raw REST snapshot and a full field inventory of the
  last companion frame, including fields the integration does not decode.
  Appliance, session and probe identifiers are redacted.
• Cook mode table in the README, mapping the raw values (0–10) to the cloud's
  own names.

Fixed

• Rotated refresh tokens are now persisted. The client adopted a rotated token
  in memory only, so a restart fell back to one the cloud had already retired and
  authentication failed. The README's claim that the token "does not rotate" was
  wrong and has been corrected.

Notes

Still read-only, still single-session (cannot run alongside the official app), and
the probe target remains unavailable — the cloud does not carry it.