Add support for TC39 Temporal API

Feature Description

JavaScript's built-in Date object makes it difficult to clearly handle time zone-aware date/time values, time-only values, and date-only values.

Because a single Date type is used for all of these cases, timezone handling and conversion logic can become confusing and error-prone.

Temporal would provide a more explicit and reliable way to represent these date/time use cases.

Temporal has also reached TC39 Stage 4 and is now part of the JavaScript standard.

The Solution

The Solution

@Entity()
export class Schedule {
  @PrimaryGeneratedColumn()
  id: number;

  @Column()
  date: Temporal.PlainDate;

  @Column()
  startedTime: Temporal.PlainTime;

  @Column()
  endedTime: Temporal.PlainTime;

  @Column()
  startedAt: Temporal.ZonedDateTime;
}

Considered Alternatives

• Continue using Date with custom transformers
• Store Temporal values as strings and convert them manually

These approaches work as a workaround, but they still require repetitive conversion logic and do not provide a first-class, type-safe Temporal integration.

Additional Context

No response

Relevant Database Driver(s)

• aurora-mysql
• aurora-postgres
• better-sqlite3
• capacitor
• cockroachdb
• cordova
• expo
• mongodb
• mysql
• nativescript
• oracle
• postgres
• react-native
• sap
• spanner
• sqlite
• sqljs
• sqlserver

Are you willing to resolve this issue by submitting a Pull Request?

Yes, I have the time, but I don't know how to start. I would need guidance.

The issue names TypeScript entity fields and the MySQL and PostgreSQL drivers, but no files, tests, or entry points. Start by tracing existing Date column handling for those drivers and defining mappings for the listed Temporal types; done means Temporal-valued entity columns work correctly with the requested database types and are covered by tests.