feat(DateTime2): export TimePicker

[bvandercar-vt]

Fixes #6739

Checklist

• [N/A] Includes tests
• [N/A] Update documentation

Changes proposed in this pull request:

Export TimePicker from datetime2 package, from the original datetime package, like is already being done for TimezoneSelect as well as other componentes/ types.

Reviewers should focus on:

Other components/types are exported this way in the same file

[changelog-app]

Generate changelog in packages/datetime2/changelog/@unreleased

What do the change types mean?

• feature: A new feature of the service.
• improvement: An incremental improvement in the functionality or operation of the service.
• fix: Remedies the incorrect behaviour of a component of the service in a backwards-compatible way.
• break: Has the potential to break consumers of this service's API, inclusive of both Palantir services
  and external consumers of the service's API (e.g. customer-written software or integrations).
• deprecation: Advertises the intention to remove service functionality without any change to the
  operation of the service itself.
• manualTask: Requires the possibility of manual intervention (running a script, eyeballing configuration,
  performing database surgery, ...) at the time of upgrade for it to succeed.
• migration: A fully automatic upgrade migration task with no engineer input required.

Note: only one type should be chosen.

How are new versions calculated?

• ❗The break and manual task changelog types will result in a major release!
• 🐛 The fix changelog type will result in a minor release in most cases, and a patch release version for patch branches. This behaviour is configurable in autorelease.
• ✨ All others will result in a minor version release.

Type

• Feature
• Improvement
• Fix
• Break
• Deprecation
• Manual task
• Migration

Description

feat(DateTime2): export TimePicker

Check the box to generate changelog(s)

• Generate changelog entry

[evansjohnson]

Thanks for looking into this! I've found the lack of consistency here confusing in the past as well.

I imagine the original intent was to push users to import from datetime, as that is ultimately the package users will import all of these from, but I think the partial re-export state is more confusing than is worth it to push users to datetime imports early.

[evansjohnson]

thanks for taking another pass! happy to approve if we add deprecation messages back

with that I'm leaning towards respecting existing behavior more so than actually thinking they're helpful, but I do see some argument for them which I left in the comment

[evansjohnson]

I would be in support of improving this deprecation message with an "or preferably use ___3"

[bvandercar-vt]

just changed it back to the old one

[evansjohnson]

huh, do you know what this was needed for?

[bvandercar-vt]

The test was failing and MonthAndYear is also excluded in the same place in /datetime/test/isotest.mjs