Write INFO logs for components transitioning to WORKING state

[shsms]

No description provided.

[Copilot]

Pull Request Overview

This PR changes the log level for component status transitions from NOT_WORKING to WORKING state from WARNING to INFO level. This adjustment better reflects that transitioning to a WORKING state is normal operational behavior rather than a warning condition.

• Changed log level from warning to info for WORKING state transitions
• Applied the change consistently across PV inverter and EV charger status trackers

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
_pv_inverter_status_tracker.py	Updated log level to INFO when PV inverter transitions to WORKING state
_ev_charger_status_tracker.py	Updated log level to INFO when EV charger transitions to WORKING state

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[llucax]

Wouldn't it make sense to also say it's becoming functional after being not working? Or at least say "changed state to WORKING` or something like that, saying more explicit it is a state change?

[shsms]

Done

[Marenz]

I personally hate the release notes update in an extra commit 😆

[shsms]

Any nasty trick to stay ahead of @llucax: https://github.com/frequenz-floss/frequenz-sdk-python/graphs/contributors \o/