Add support for Temporal API

### Which @angular/* package(s) are relevant/related to the feature request?

_common_

### Description

The Temporal API reached TC39 Stage 4 in March 2026 and is now part of ES2026. It's shipping natively in Firefox 139+, Chrome 144+, and Edge 144+, with Node.js 26+ enabling it unflagged, and TypeScript 6.0 ships built-in types under `esnext.temporal`. Safari currently only has partial support in Technology Preview, so it's clearly not yet a baseline that Angular could require but the trajectory suggests full cross-browser support isn't far off.

This isn't a request to ship full Temporal support in `DatePipe` today. It's a proposal to start thinking about the design now, so that when Safari catches up, Angular is ready to fully support it.

I'm happy to help with the design discussion and, if the proposal is accepted and the timing is appropriate, I'd also be interested in working on an implementation.

### Proposed solution

Open a discussion on how `DatePipe` *would* extend to accept `Temporal.PlainDate`, `Temporal.PlainDateTime`, `Temporal.ZonedDateTime`, and `Temporal.Instant` inputs.

### Alternatives considered

- Wait until Safari ships full support before discussing anything.
- A separate `TemporalPipe` or `TemporalDatePipe`.
- Leaving `DatePipe` as it is.

Inizia esaminando il punto di ingresso di DatePipe di Angular e i suoi attuali tipi di input e comportamento nella gestione delle date. Confronta i casi proposti per Temporal.PlainDate, Temporal.PlainDateTime, Temporal.ZonedDateTime e Temporal.Instant, quindi documenta una direzione API definita; questo issue non identifica file o test specifici per l'implementazione.

Scritto dal modello di indicizzazione a partire dal testo della issue.