Go eyes standard UUID package

This is small on paper but meaningful in practice: when a utility package graduates into the Go standard library, it usually means the ecosystem has converged and the maintenance burden of third-party dependency sprawl can shrink.

• –UUID handling is table-stakes infrastructure for APIs, databases, and distributed systems, so standardizing it removes one of the most common “why isn’t this in stdlib?” gaps in Go
• –The proposal explicitly leans on stable, familiar API patterns from the widely used `google/uuid` package, which should lower migration friction
• –Landing under `crypto/uuid` also signals Go wants secure defaults for random UUID generation rather than leaving teams to make that choice ad hoc