Add TimeField component

[mkernohanbc]

This PR adds a new TimeField component (based on RA TimeField), building on work done by @raarielgrace as part of DDS' hackathon.

TimeField follows the pattern of other BCDS input components:

A value can be entered by:

• Typing digits into each segment
• Using the arrow keys to increment/decrement each segment's value

Like DatePicker, TimeField is designed to work with objects from @internationalized/date.

By default a TimeField:

• Uses 12-hour time (toggleable via hourCycle)
• Accepts an hour and minute value (can be configured to hour-only or second via granularity)
• Appends a time-zone abbreviation (toggleable via hideTimeZone)
• Does not show leading zeroes (toggleable via shouldForceLeadingZeros)

Like other components, it supports medium/small sizes, and required/disabled/read-only/invalid states. A TimeField's value can be set or reading using value, and constrained using minValue and maxValue.

[ty2k]

This is awesome! Very minor changes requested below, and a couple comments beyond the scope of this PR.

[ty2k]

We might also want a rule here that accounts for the disabled input case:

[ty2k]

Minor thing that's annoying with the time zone thing, it's focus-able and looks just like the rest of the fields but can't actually be changed in this example (the example in the Storybook with this text above it: "The granularity prop sets the smallest unit. Choose from hour, minute (default) or second:").

Screen.Recording.2026-03-10.at.8.46.10.PM.mov

I don't think there's much to be done here. We could write a CSS rule for when aria-readonly="true", I guess? But it seems like timezones are not going to be much of a concern for us going forward. Maybe not worth thinking about.

[mkernohanbc]

Yeah, this is an odd thing — there is no concept anywhere in the API of the time-zone being a thing the user sets manually, so it being a focusable segment is a bit strange.

Made a change in 25ff9d2, tweaking the styling of that specific segment to at least give a bit of a cue that this is Different to the others:

[mkernohanbc]

I've also fixed the [data-disabled] case — the time-zone now follows the styling of the rest of the segments.

[ty2k]

Minor thing here we can't do anything about it (AFAIK), but I can't for the life of me actually highlight and copy the text in the input field without copying the label and description also:

Screen.Recording.2026-03-10.at.9.00.07.PM.mov

When I do that and paste into VS Code, I get the Unicode "pop directional isolate" character coming along for the ride:

[mkernohanbc]

you are not alone on this one: adobe/react-spectrum#5285