OCPP: handle firmware management events

[andig]

Adds the OCPP 1.6 FirmwareManagement profile and acknowledges FirmwareStatusNotification and DiagnosticsStatusNotification so chargers no longer trigger NotSupported errors when reporting firmware/diagnostics status (e.g. ABL Pulsar Plus on FW 6.11.25).

Same pattern as #23199 (security profile).

Closes #29495

[sourcery-ai]

Hey - I've left some high level feedback:

• Right now the firmware and diagnostics status notifications are simply acknowledged and discarded; consider at least logging the reported status or updating some internal state so that firmware/diagnostics progress can be inspected or acted upon later.
• If certain firmware or diagnostics statuses are unexpected or undesired (e.g. repeated failures), it might be useful to validate request.Status and apply different handling or warnings rather than treating all notifications identically.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Right now the firmware and diagnostics status notifications are simply acknowledged and discarded; consider at least logging the reported status or updating some internal state so that firmware/diagnostics progress can be inspected or acted upon later.
- If certain firmware or diagnostics statuses are unexpected or undesired (e.g. repeated failures), it might be useful to validate `request.Status` and apply different handling or warnings rather than treating all notifications identically.

---

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.}