Fixing calculation of getFireTimeAfter in CalendarIntervalTriggerImpl

[okokhanyy]

This PR addresses the following shortcomings with CalendarIntervalTriggerImpl.getFireTimeAfter(...):

• monthly trigger's firings starting on 31 day of month get shifted to 30th day and eventually to 28th day
• yearly trigger's firings starting on leap day of Feb 29 get shifted to 28th day of Feb
• daily trigger falling within gap daylight savings transition shifts forward by one hour following the transition

Fix #1352
Fix #1444

Changes

• refactored CalendarIntervalTriggerImpl.getFireTimeAfter to use LocalDateTime arithmetic
• calculating next fire time relative to trigger's startTime rather than previous fire time, that addresses issues listed above
• added unit tests for the use cases that are being addresses

---

Checklist

• tested locally
• updated the docs - NA
• added appropriate test
• signed-off on the DCO referenced in the CONTRIBUTING link below via git commit -s on my commits, and submit this code under terms of the Apache 2.0 license and assign copyright to the Quartz project owners
  (If you're not using command-line, you can use a browser extension )

---

In submitting this contribution, I agree to the terms of contributing as referred to here:
https://github.com/quartz-scheduler/contributing/blob/main/CONTRIBUTING.md