Relax type constraints for components passed to createRoutesStub

[rossipedia]

Related bug: #14886

TL;DR:
You can't pass a Route component directly to createRoutesStub if it uses the generated Route.ComponentProps type.

There's a StackBlitz link in that issue that demonstrates the type error.

I think that createRoutesStub should allow any React component to be passed directly for the Component property of a stubbed route.

In specific implementation terms, that means:

interface StubRouteExtensions {
- Component?: RouteComponentType;
+ Component?: React.ComponentType<any>;
  HydrateFallback?: HydrateFallbackType;
  ErrorBoundary?: ErrorBoundaryType;
  loader?: LoaderFunction;
  action?: ActionFunction;
  children?: StubRouteObject[];
  meta?: MetaFunction;
  links?: LinksFunction;
}

Typescript is trying to be correct here, but I think in this situation it's not really viable: createRoutesStub can't realistically know every possible Route.ComponentType for every component that might be passed to it. So instead, it should accept any kind of component, and do its best to render it as a route component.

This also lets "pre-typegen" prop-less route components that are currently passed directly into createRoutesStub migrate to Route.ComponentProps without extensive hoop-jumping that would be required today.

For example:

import { createRoutesStub } from "react-router";
import { test } from "vitest";

import ProductRoute from "~/routes/product";
- import type { Route } from "../.react-router/types/app/routes/+types/product";

test("it works", async () => {
  let Stub = createRoutesStub([
    {
      id: "root",
-     Component: (props) => (
-       <ProductRoute {...(props as Route.ComponentProps)} />
-     ),
+     Component: ProductRoute,
    },
  ]);
});

I initially tried going down the path of making createRoutesStub generic, something like createRoutesStub<RouteConfig extends StubRouteObject[]>(), but it becomes a recursive type-definition problem, since you have to define children as generic as well, and that type needs to extend StubRouteObject[] as well... which is currently being defined.

While I think that approach might be solvable, it's a very complex bit of typescript-fu for very little benefit.

I also think that allowing CreateRoutesStub to render any component is pretty useful in the general case.

Most places where createRoutesStub is used is for testing/verification (ie: vites / storybook / etc...), and usually you have other things in place to give you signal that you got a prop definition wrong.