Timezone data source freshness lag relative to IANA tzdata updates

The timezone data source introduced in Terraform 1.5 retrieves offset, abbreviation, and daylight‑saving status for IANA identifiers. It depends on the Go standard library's embedded time zone database, which is updated with each Go release rather than tracking IANA tzdata publications in real time. This creates a window where recent policy changes—such as a country abolishing DST or shifting its offset—are not reflected until the next Go version ships and Terraform vendors it. Users targeting regions with frequent tzdata revisions must either accept potential hour‑level drift or layer an external lookup. The data source also accepts only IANA names, so Windows zones like Pacific Standard Time require a separate mapping step before they can be used.

• What is the typical delay between an IANA tzdata release and its availability in a stable Terraform build?
• Are there documented workarounds for validating that the embedded database covers a specific region's latest rules without relying on external APIs?
• Does the data source surface any metadata indicating the tzdata version it was built against?