fix!: disable HTTP redirects in restricted networking implementation

[ok-nick]

Disables HTTP redirects in the built-in networking implementation. The built-in WASM/WASI implementation currently does not follow redirects so this change will align all platforms. To properly support redirects consistently means we have to implement our own functionality and also tie that into the restricted networking settings. I believe this is out of scope for the SDK.

A custom HTTP implementation can be user-supplied via a HTTP resolver in the Context.

[codspeed-hq]

Merging this PR will not alter performance

✅ 32 untouched benchmarks
⏩ 2 skipped benchmarks¹

---

_{Comparing ok-nick/no-redirects (2b1061e) with main (e0e4cc2)}

Footnotes

1. 2 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. ↩

[ok-nick]

TODO: Change behavior to only disable redirects if restricted networking is enabled after discussion with @gpeacock.

[ok-nick]

Redirects for the timestamp case will be fixed in #1855.