Config UI: fixable invalid refs

[naltatis]

fixes #24217

Make broken loadpoint references (circuit, vehicle) fixable in UI.

Note: Loadpoint/vehicle refs are already auto-removed, when you delete a vehicle via UI. However, since we support mixed setup (vehicle via yaml, lp via ui) broken refs can still happen. I've added extra handling and tests to cover this.

[sourcery-ai]

Hey - I've left some high level feedback:

• The VehicleOption type could likely be simplified to non-optional, non-nullable fields (key: string; name: string) since all current usages set both properties to concrete strings, which would tighten typing and reduce null/undefined handling overhead.
• The invalidCircuit and invalidVehicle computed properties share the same pattern of reference validation; consider extracting a small reusable helper (e.g., isInvalidReference(value, options)) to reduce duplication and keep the logic consistent if it evolves.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The `VehicleOption` type could likely be simplified to non-optional, non-nullable fields (`key: string; name: string`) since all current usages set both properties to concrete strings, which would tighten typing and reduce `null`/`undefined` handling overhead.
- The `invalidCircuit` and `invalidVehicle` computed properties share the same pattern of reference validation; consider extracting a small reusable helper (e.g., `isInvalidReference(value, options)`) to reduce duplication and keep the logic consistent if it evolves.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}