v2.0.4 — Benchmark PV sensor unique_id fix

🐛 Fix

BenchmarkAnnualPVSensor used the same entity key ("PV Produktion") as PVProductionSensor, causing a unique_id collision. The benchmark sensor was silently dropped on startup with this warning:

Platform pv_management_fix does not generate unique IDs.
ID pv_management_fix_pv_management_pv_produktion already exists
— ignoring sensor.pv_management_pv_produktion

What changed

• Renamed the benchmark sensor key from "PV Produktion" → "PV Produktion Benchmark"
• Translation keys (pv_produktion_benchmark in de/en/pl) were already in place — no translation work needed

What this means for you

• Existing sensor.pv_management_pv_produktion stays unchanged — same unique_id, same name, same history
• A new sensor for the extrapolated annual benchmark PV production will appear (only if you have benchmark mode enabled)
• No breaking changes, no manual migration required

Commits

• c0f9825 fix: rename benchmark PV sensor key to avoid unique_id collision