[RAC Feature Request]: Opt-in single tab stop for DatePicker / DateField / TimeField

### Provide a general summary of the feature here

Introduce an opt-in prop for date and time field components that implements a single tab stop pattern.

### 🤔 Expected Behavior?

- Tab: Moves focus into the field (landing on the first segment or the entire input).
- Arrow Left / Right: Moves focus between the internal segments (like it does now already)
- Tab (again): Exits the field and moves to the next focusable element in the DOM.

### 😯 Current Behavior

Users have to press Tab key 3 to 4 times to navigate through a single date or time field.

### 🔦 Context

In data-entry heavy applications, requiring users to press the Tab key 3 to 4 times to navigate through a single date / time field causes significant "Tab fatigue." For power users filling out large forms, this default segmented tabbing behavior severely slows down keyboard navigation compared to standard text inputs.

Start at the DatePicker, DateField, and TimeField component entry points and trace their current segmented keyboard and focus behavior. Define the opt-in single-tab-stop behavior consistently across the three components, preserving arrow-key movement between segments, and verify that Tab enters once and then exits to the next focusable element.

Written by the indexing model from the issue text.