Remove experimental gate from snapshots API

[gpanders]

Remove the experimental gate from the snapshots API so that it's ready to use by external users before Agents week.

cc @mikenomitch

[ask-bonk]

The flags variable is still used for hardTimeout and req.setCompatibilityFlags(flags) so it's still needed. Good.

Now let me verify the overall picture is clean. The changes are:

1. C++ (container.c++): Removed the getWorkerdExperimental() gate around directorySnapshots and containerSnapshot handling in start(). The code is otherwise identical, just de-indented.

2. C++ (container.h):

   • Removed JSG_STRUCT_TS_OVERRIDE_DYNAMIC from DirectorySnapshot, DirectorySnapshotOptions, DirectorySnapshotRestoreParams, Snapshot, and SnapshotOptions structs (these were setting them to never when not experimental).
   • Updated StartupOptions TS override to show real types instead of never for directorySnapshots and containerSnapshot.
   • Moved snapshotDirectory and snapshotContainer out of the if (flags.getWorkerdExperimental()) block in JSG_RESOURCE_TYPE.

3. Types: Generated type snapshots updated to reflect the above (snapshot types now appear in latest/, method order adjusted in experimental/).

This all looks correct and straightforward. The change is self-consistent: the snapshot API methods and types are un-gated from experimental, while interceptOutboundHttps and hardTimeout remain experimental-only.

One thing I notice: this is a behavioral change (new API surface for non-experimental users), but since this is removing an experimental gate (making previously-experimental-only features generally available), it doesn't need a compat flag. Experimental features are explicitly not covered by backward compatibility guarantees.

LGTM

github run