fix(datetime): minutes only filtered when max hour matches current hour

[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 max value for ion-datetime will filter the minute selection for all hours. This means if the max value is "19:30", users are only able to select minutes 0-30 within hour 19 (correct), but when within hour 18, they are still only able to select minutes 0-30 (incorrect).

Issue Number: #24702

What is the new behavior?

The max time constraint will only filter minute selections when the max time hour matches the current hour. This means that when max constraint is "19:30" and the hour is 19, users will only be able to select 0-30. When the hour is 18, users will be able to select 0-60.

Does this introduce a breaking change?

• Yes
• No

Other information