fix(remix): Match the Remix 3.0.0 package versions (#25008)

Remix 3.0.0 bumped `@remix-run/fetch-router`, `@remix-run/assets` and
`@remix-run/node-fetch-server` from 0.x to 1.0.0, and renamed
`@remix-run/ui` to `@remix-run/component`. Our orchestrion ranges ended
at `<1`, so on 3.0.0 nothing was instrumented: no route names, no server
errors, no debug IDs, and no render errors from the renamed runtime.

The ranges now end at `<2`, and `run` is also matched in
`@remix-run/component`. The client subscribes to both `run` channels; an
app has only one of them. Module paths and signatures did not change,
which the e2e suite on `remix@3.0.0` confirms.

The e2e app moves to 3.0.0. Its document now renders the entry's import
map, because the 3.0.0 asset server no longer rewrites bare imports.
That is a Remix change every app makes, not an SDK one.

Fixes #25007

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>