containers: intercept http gets out of experimental land

[gabivlj]

No description provided.

[ask-bonk]

The change is very small and clean. Let me verify there are no other concerns:

1. Two methods (interceptOutboundHttp, interceptAllOutboundHttp) are being ungated from getWorkerdExperimental() in the JSG_RESOURCE_TYPE registration.
2. Type snapshots are updated in latest/ to include these methods (they were already in experimental/).
3. The implementation in container.c++ has no experimental gating — the methods themselves never checked getWorkerdExperimental() at runtime, only the JSG registration was conditional.

This is a straightforward promotion of two methods from experimental to stable. The Container API is already a non-experimental feature (most methods are unconditionally registered), and these two methods are simply joining the rest. There are no backward compatibility concerns since this is purely additive — methods that were only available with the experimental flag are now available to everyone.

No issues found with this change.

LGTM

github run

[codspeed-hq]

Merging this PR will improve performance by 26.58%

⚡ 1 improved benchmark
✅ 69 untouched benchmarks
⏩ 129 skipped benchmarks¹

Performance Changes

	Benchmark	BASE	HEAD	Efficiency
⚡	bodyWithHeaders[Response]	38.6 µs	30.5 µs	+26.58%

---

_{Comparing gv/upgrade-from-exp (77feeb0) with main (2536901)}

Footnotes

1. 129 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩