File based routing more default file name options for code splitting and generation

[ViewableGravy]

I honestly just assume I am blind and someone has suggested this before, so sorry in advance if this is a duplciate.

At the moment, there are essentially four file names that have a meaning in tanstack router:

1. route.ts(x)
2. index.ts(x)
3. route.lazy.ts(x)
4. index.lazy.ts(x)

Index producing the direct route (no outlet), and route producing a layout route (outlet).

It seems intuitive to me, that this idea would be extended to support the following route file naming, since components do not dictate the type of the router:

1. index.pending.ts & route.pending.ts
2. index.error.ts & route.error.ts
3. index.component.ts & route.component.ts

These would be files that contains the pending, error and component components for their respective routes, and would automatically have a template simliar to the below

const Route = getRouteAPI(%%tsrPath%%)

export function %%tsrComponentType%%RouteComponent() {
  return <div>Hello from %%tsrPath%%</div>
}

In cases where we have an extremely long loader function, or a lot of search schema logic, the route component file can become quite large. Sometimes reaching over 100 lines of just createFileRoute. At least in our code base, we try to aim to keep components and files under 100 lines where possible, so it seems obvious at that point that we'd want to abstract the components to another file. While this is completely doable, and we can easily name our files -index.pending.ts or even create a custom ignore rule for these files from the autogeneration - this actually seems like something that tanstack router would want to target.

I'm not a huge user of NextJS, but my understanding is they have something similar in their routing system, so it may also make the transition across easier for people if these options existed.