Small health check improvements

[Donnerbart]

We're digging into a reported operator health issue right now, and I noticed the for for typo in the debug log.

I also noticed a RetryAndRescheduleTimerEventSource with status UNKNOWN in the event source health indicators, caused by TimerEventSource not implementing the getStatus() method. If that was intentional (since we don't know if the actual timer tasks have been executed successfully), I can drop that commit again.

[Copilot]

Pull Request Overview

This PR fixes a typo in a debug log message and implements the getStatus() method for TimerEventSource to properly report health status instead of defaulting to UNKNOWN.

Key Changes:

• Corrected "for for" typo in InformerWrapper debug log
• Implemented getStatus() method in TimerEventSource to return HEALTHY/UNHEALTHY based on running state
• Refactored InformerWrappingEventSourceHealthIndicator to use more concise stream operation

Reviewed Changes

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

Show a summary per file

File	Description
TimerEventSource.java	Adds getStatus() method implementation to report HEALTHY when running, UNHEALTHY when stopped
TimerEventSourceTest.java	Adds assertions to verify status is HEALTHY/UNHEALTHY in appropriate test scenarios
InformerWrapper.java	Fixes typo "for for" → "for" and adjusts spacing in debug log message
InformerWrappingEventSourceHealthIndicator.java	Simplifies stream logic using anyMatch instead of filter/findAny
PollingEventSourceTest.java	Removes unnecessary throws declaration from test method

---

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

[csviri]

Hi @Donnerbart I think this is reasonable to change it this way. Thank you!

[csviri]

LGTM

[csviri]

I did not checked yet, but this might be also interesting:
#2978

[csviri]

thank you @Donnerbart !