Support `Temporal` across Node.js APIs

The [`Temporal` proposal](https://github.com/tc39/proposal-temporal) is currently Stage 3, has `in progress / experimental` implementation in V8 (available in latest releases using `--harmony-temporal`), and is likely to be unflagged in Node.js once it's stable enough (refs: https://github.com/nodejs/node/issues/57127, https://github.com/nodejs/node/pull/57128). In light of this, I propose that Node.js begins supporting `Temporal` in the relevant APIs (mainly those that already work with `Date`s) after it becomes available by default without runtime flag. Relevant APIs: - [x] `fs`: `Stats` and `BigIntStats` Only bigint version provides nanosecond precision, and both provide lazy getters for `Date` instances. Adding lazy getters for `Temporal.Instant` would also make non-bigint version provide nanosecond precision. - [ ] `fs`: `utimes()`, `lutimes()`, `futimes()`, `utimesSync()`, `lutimesSync()`, `futimesSync()`, `promises.utimes()`, `promises.lutimes()`, `filehandle.utimes()` Accepts `atime` and `mtime` as `number`|`string`|`Date`, can support `Temporal.Instant` as well. Note: these functions also don't accept `bigint`s yet. In the Temporal API, `number`s are used for `epochTime`s in milliseconds while `bigint`s are used for nanoseconds. Adding direct support of `bigint`s might result a confusing API: some users might expect it to coerce type and behave exactly the same as `number`|`string`, some might expect it to be parsed as nanoseconds. Adding `Temporal` support would make it unambiguous. Maybe there are other APIs that can benefit from this, too? cc @nodejs/fs since it's only https://github.com/nodejs/node/labels/fs at the moment. Internal updates (if it happens to be more precise, more fast, or more readable), generic support (primordials, `util`, `assert`, etc.) and dependencies (for example, `undici.setCookie(, { expires })`) are out of scope here.