notify: use tick time in dedup repeat checks

[KyungHwanKim-devs]

Summary

• Use dispatcher tick time (context Now) for dedup repeat-interval checks.
• Add a regression test ensuring dedup honors the context time source.
• Update changelog.

Background

Issue #2461 reports TestRetry consistently failing on Darwin due to repeat notifications occurring earlier than expected.

Root Cause

DedupStage relied on time.Now() instead of the dispatcher-provided tick time. When the pipeline execution is delayed on Darwin, the repeat interval appears to have already elapsed, causing an early resend.

Fix

DedupStage now prefers the context Now value (set by dispatch) and falls back to its internal clock when absent, making repeat-interval decisions deterministic.

Testing

• make test (macOS: ld LC_DYSYMTAB warnings)

Fixes #2461.

[ultrotter]

I don't fully love it as it's quite manual and easy to forget the overridden time.
But perhaps it's fine so far, and anyway we can evaluate moving to synctest avoiding manual time mocks, after the next go version is released.

[Spaceman1701]

I don't fully love it as it's quite manual and easy to forget the overridden time. But perhaps it's fine so far, and anyway we can evaluate moving to synctest avoiding manual time mocks, after the next go version is released.

I agree that this is a little ugly, but I think it's the intended way to get the time in a notification pipeline. I wonder if it'd be a little cleaner to make DedupStage.now take a ctx and encapsulate the behavior of finding the time from the context.

[Spaceman1701]

I forgot to approve before, but I think this is good to merge as is.

@KyungHwanKim-devs looks like this requires a rebase. I can merge after you've done that. Thanks for the contribution!

[SoloJacobs]

I have rebased this commit. I think it is good to go.