fix(datetime): passing min/max no longer errors on missing date information

[liamdebeasi]

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)
  • Some docs updates need to be made in the ionic-docs repo, in a separate PR. See the contributing guide for details.
• 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?

Issue URL: N/A

When fixing #25833, the author reported another bug where they would get RangeError: Invalid time value at getDayColumnData when setting max="2012".

The problem is that when we clamp the date to use inside of ion-datetime, we simply return the user provided min/max datetime parts:

ionic-framework/core/src/components/datetime/utils/parse.ts

Line 120 in 2cba460

export const clampDate = (

This means that if developers pass min="2012", then the minParts object will have no information for month, day, hour, or minute.

What is the new behavior?

• Updated the min/max process logic to fill in any missing information.
• The min parts will fill in data for January 1st at 00:00. User specified data will override as available. For example, if you passed min="2012-10" you would get a min parts object for October 1, 2012 at 00:00.
• The max parts will fill in data for December 31st at 23:59. User specified data will override as available. For example, if you passed max="2022-05, you would get a max parts object for May 31, 2022 at 23:59.

Does this introduce a breaking change?

• Yes
• No

Other information