Add missing constants, stub functions, and Node.js-specific extensions
to improve compatibility with code that expects Node.js perf_hooks APIs:

- Add 13 missing constants (entry types and milestones)
- Add standalone eventLoopUtilization() and timerify() function exports
- Add nodeTiming property to the performance object (via Proxy)
- Change eventLoopUtilization() to return stub values instead of throwing
- Change markResourceTiming() to no-op instead of throwing

These changes follow the stub approach (returning default values) rather
than throwing errors, which improves compatibility with libraries that
check for API existence but may not need the actual functionality.

Per review feedback, moved nodeTiming from TypeScript Proxy wrapper to the
C++ Performance class. This makes nodeTiming available on globalThis.performance
when the enable_nodejs_perf_hooks_module flag is enabled.

Changes:
- Added PerformanceNodeTiming class extending PerformanceEntry in C++
- Added nodeTiming property to Performance class (conditional on flag)
- Removed Proxy wrapper from TypeScript, now simple re-export
- Updated type snapshots with new PerformanceNodeTiming interface

Address PR review feedback:
- Change PerformanceNodeTiming properties from prototype to instance
  properties to match Node.js behavior where Reflect.ownKeys() includes
  all properties as own properties
- Add missing uvMetricsInfo property that returns libuv event loop
  metrics (stub values since actual metrics aren't available in workerd)
- Update toJSON() to include uvMetricsInfo in the output
- Regenerate TypeScript definitions

Support tracing sqlite commit callbacks

JSG_STRUCT value types don't need memory tracking as they are passed
by value to/from JavaScript and don't persist as embedder objects.

Autogate is fully rolled out

…Source (#5427)

Use the generic MemoryInputStream to provide the stream for blob data
with autogate

* Move the daily release compat date 7 days into the future

* Check for future dates as well

* Make message more verbose

* Fix compatibility-date-test expectations for new future date check

…oks-compat

fix(perf_hooks): improve Node.js perf_hooks compatibility

Co-authored-by: alistairjevans <alistair@betterstack.com>

- Ideally we'd enable this on all C/C++ code, but that's difficult (see TODO
  comment)
- This should fix #5977 by ensuring both places where we
  compute SQL-related hashes use hardware acceleration. To address this more
  generally, we'll need to make changes in capnp (capnproto/capnproto#2564)
- Also fixes a regression where crc-impl.c++ was compiled without CRC extensions
  enabled, which appears to have caused the software-based CRC32C implementation
  to be used
- Define -O3 properly for perfetto-tracing target on Windows, for consistency

Includes a fix to an already existing bug that when piping a readable
stream through a transform stream, and the transform's readable
side is canceled, the source readable would not be correctly
released and marked as closed. With this fix, verified that the
behavior is correct per the spec and matches other implementations.
Should not be a breaking change as this as previously broken and
would error in inconsistent ways (IdentityTransformStream would
error differently than a regular TransformStream), now both have
consistent and correct behavior.