This PR adds parameterized routes for Remix SDK, similarly to the NextJS SDK

Resolves: #16690
Needs docs PR for the Vite plugin

Adds automatic parameterization of Remix route IDs for transaction naming. Converts internal Remix route file patterns to parameterized paths similar to the other SDKs (routes/user.$id -> /user/:id).

• Created sentryRemixVitePlugin that extracts route information from Remix builds and generates a manifest file containing route ID to parameterized route mappings.
• Added remixRouteParameterization.ts with regex-based route conversion that handles dynamic segments ($param → :param), splat routes ($ → :*), and nested routes.
• Updated both client and server instrumentation in performance.tsx and instrumentServer.ts to use parameterized transaction names.
• It also works with Hydrogen

Vite plugin is used like:

// vite.config.ts
import { defineConfig } from 'vite';
import { vitePlugin as remix } from '@remix-run/dev';
import { sentryRemixVitePlugin } from '@sentry/remix';
export default defineConfig({
 plugins: [
 remix(),
 sentryRemixVitePlugin({
 appDirPath: './app', // Default is 'app' in project root
 }),
 ],
});

Updated all Remix E2E test applications to expect parameterized route names. Added new E2E test application create-remix-app-v2-non-vite for testing backward compatibility for non-Vite builds - these continue to use routes/user.$id format.

Summary

• Legacy Remix applications (non-Vite) will continue to work without changes.
• For backward compatibility, Vite projects that are not using the plugin will behave like before.