Add immediate firing capability for time alerts and corresponding test

[stastnypremysl]

Summary

This pull request introduces a new feature to handle cases where a time alert is set for the exact current time in the TestClock implementation. It ensures that such alerts fire immediately and includes corresponding unit tests to validate this behavior.

Bug fix: Immediate Firing for Current Time Alerts

• crates/common/src/clock.rs: Modified the TestTimer::new invocation to include a new fire_immediately parameter, which is set to true when the alert time equals the current time. This ensures immediate firing of the alert.

Type of change

• Bug fix (non-breaking)
• New feature (non-breaking)
• Breaking change (impacts existing behavior)
• Documentation update
• Maintenance / chore

Release notes

• I added a concise entry to RELEASES.md that follows the existing conventions (when applicable)

Testing

Ensure new or changed logic is covered by tests.

• Affected code paths are already covered by the test suite
• I added/updated tests to cover new or changed logic

Testing Enhancements

• crates/common/src/clock.rs: Added a new test case, test_set_time_alert_when_alert_time_equals_current_time, to verify that alerts set for the current time fire immediately. This test checks the timer count, advances the clock, and asserts the correct event behavior.# Pull Request

[CLAassistant]

All committers have signed the CLA.

[Copilot]

Pull Request Overview

This PR adds support for firing time alerts immediately when the alert time matches the current time and includes a unit test to validate this behavior.

• Added a fire_immediately flag in TestTimer::new when alert_time_ns == ts_now
• Updated the TestTimer instantiation to pass the new flag
• Introduced test_set_time_alert_when_alert_time_equals_current_time to verify immediate firing

[cjdsellers]

Thanks for the fix @stastnypremysl