fix(datetime): navigate to month within min range

[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?

When providing a min value to ion-datetime that includes a day, the month of the min value will be disabled and once you have navigated away from it, you will be unable to return to it.

This is because the isBefore/isAfter checks additionally compare the day value, when min/max includes it. This is correct for date comparisons, but isn't a 1:1 with rules surrounding disabling months.

Issue Number: #24757

What is the new behavior?

Users can navigate to min/max months, when the min/max value includes a day constraint.

i.e.: If the min is 2022-02-09, users should still be able to navigate to February, since days 10-28 are enabled.

Does this introduce a breaking change?

• Yes
• No

Other information

[liamdebeasi]

Can we add comments to the code as to why we are passing in day: null? Otherwise this looks good.