feat(rsc): ability to not load server reference module during createFromReadableStream on rsc environment

[hi-ogawa]

Description

• related feat(rsc): ability to preserve decoded server references #1253

TODO:

• e2e (payload producer and reviver in different runtime and verify module not loaded on reviver end)
• docs

This PR adds createFromReadableStream options { preserveServerReferences: true } to allow not loading server reference module. The use case is demonstrated in packages/plugin-rsc/examples/cache-replay and accompanying e2e. In short, it allows rsc flight payload produced by one runtime to be consumed by other runtime and render it as a form action without importing associated server reference module.

The implementation idea is a same as $$decode-client proxy trick we already use for preserving client reference "entity" without reviving actual "module" during createFromReadableStream. This PR added $$preserve tag for server reference. This idea is illustrated in https://artifacts.hiro18181.workers.dev/vite-plugin-react-rsc-load-id-journey (this was created before this PR, so missing $$preserve mention).

This is a smaller scope of changes from #1253 where I can understand the motivation and verify the correctness. The other aspect from the original PR such as framework-owned reference format seems to have issues in entire usages of server action lifecycle (from my reading, the e2e there doesn't support progressive enhancement form action since it only intercepts loadServerAction), so it's deferred and will be investigated separately.

For further context that I haven't fully verified in my eye but raised by agents are following:

• Next.js doesn't have a similar mechanism and its cache reply does resolve server action module. So this rsc bundler concept seems specific to rsc plugin.
• Also the dump of local notes as gist https://gist.github.com/hi-ogawa/4d3d734f688c938045a6e199540830b9