fix(datetime): years displayed now more consistent with v5 datetime, max and min are now accounted for in MD mode

[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)
• 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 Number: resolves #23615

What is the new behavior?

• Max/Min are now accounted for when generating years in MD mode
• Out of bounds years are no longer shown in MD mode, making behavior more consistent with iOS mode
• Datetime renders max year as current year and min year as current year - 100 by default for better consistency with old datetime behavior.
• I also changed the internals so that the years array is passed into the ios and MD functions so something like this doesn't happen again

Does this introduce a breaking change?

• Yes
• No

Other information

[willmartian]

Nice work! 💯