Create separate API route for each trpc router

[keithwillcode]

What does this PR do?

Separates all tRPC routers into their own subfolders so we only load the dependencies needed per router instead of for all of them.

Environment: Staging(main branch) / Production

Type of change

• Chore (refactoring code, technical debt, workflow improvements)

How should this be tested?

Need to test basically the entire app.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
cal	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 29, 2023 10:56pm
ui	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 29, 2023 10:56pm

[keithwillcode]

This started out as a separate experiment for the public router but is truly an extension of #8041 so if we choose this path, I will cherry-pick commits over to that PR to build on @juliusmarminge work.

[keithwillcode]

Initial tests are showing that this does in fact make a massive different on cold starts. We didn't see the benefits in #8041 because it only separated the slots router out. In my initial follow up experiment, separating the public tRPC router to a subfolder resulted in a cold start load time of public.viewer.i18n of 2 seconds instead of 15+.

[keithwillcode]

Closing this because all work now going into #8041