fix: preserve the cause of turbo-stream decode failures

[Jiralite]

I, personally, am uncommonly catching these errors in Sentry. I would like to debug further, but I cannot, because the actual error is not surfaced.

This pull request attaches a cause to the error to help surface the issue.

This pattern is already used elsewhere in the codebase:

react-router/packages/react-router/lib/rsc/browser.tsx

Lines 644 to 651 in 2e0bf72

	} catch (cause) {
	// Can't clone after consuming the body via decode so we can't include the
	// body here. In an ideal world we'd look for an RSC content type here,
	// or even X-Remix-Response but then folks can't statically deploy their
	// prerendered .rsc files to a CDN unless they can tell that CDN to add
	// special headers to those certain files - which is a bit restrictive.
	throw new Error("Unable to decode RSC response", { cause });
	}