fix(datetime): arrow navigation respects min/max values

[sean-perkins]

Pull request checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
• Build (npm run build) was run locally and any changes were pushed
• Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

The value of the ion-datetime, when used with min or max, can incorrectly disable the next/previous navigation. When selecting a date such as "March 20th, 2022", but having a max date of "April 19th, 2022"; the existing comparison logic would disable the next button, since the 1 month offset was April 20th, which was beyond the max value. The same behavior happened for min values.

Issue URL: #25073

What is the new behavior?

When calculating if the next or previous button should be disabled, it will ignore comparison on the day of the month and only compares if the month & year are within bounds (for next/previous navigation).

Does this introduce a breaking change?

• Yes
• No

Other information

Dev-build: 6.1.3-dev.11650654723.120c74ee ✅

Reproduction repo: https://github.com/sean-perkins/ion-datetime-min-max-25073 (uses dev build).

[liamdebeasi]

Can you write some tests?