test: resolve issues with tests and crossing a DST boundary

[JohnVillalovos]

Tests were failing as the range they were using was crossing a Daylight Savings Time (DST) boundary. Switch those tests to use a fixed date/time.

[Copilot]

Pull request overview

Updates a few reservation-related tests to avoid flakiness caused by date math crossing a DST boundary by freezing the global Date::Now() value to a fixed midday timestamp.

Changes:

• Freeze Date::Now() to a fixed timestamp in testBindsToClosestPeriod().
• Freeze Date::Now() to a fixed timestamp in testBindsToClosestPeriodFromReservationDates().
• Freeze Date::Now() to a fixed timestamp in testMaxNoticeIsCheckedAgainstEachReservationInstanceForEachResource().

Reviewed changes

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

File	Description
tests/Presenters/Reservation/ReservationInitializationTest.php	Freezes Date::Now() for the “closest period” binding test to avoid DST-boundary flakiness.
tests/Presenters/Reservation/ExistingReservationInitializerTest.php	Freezes Date::Now() for the “closest period from reservation dates” test to avoid DST-boundary flakiness.
tests/Application/Reservation/ResourceMaximumNoticeRuleTest.php	Freezes Date::Now() for the max-notice validation test to keep repeat-instance date generation deterministic.

---

You can also share your feedback on Copilot code review. Take the survey.