feat(ant-stack): implement route creation logic

[ecxyzzy]

Notable changes:

• Removed the background colors because the text with them were either illegible or made my eyes bleed. Generally I prefer minimal use of colors, even for a CLI tool, like how pnpm does it (as shown below).
• Removed non-interactive route creation. We can add it back in later, but I feel that a tool like this should focus on DX, which means prioritizing interactivity.
• Removed DATABASE_URL_SCRAPER from the env. Normal members are not going to have access to it, and they don't need it for API route development anyways, which is what AntStack is for.

Caveats:

• I'm not sure how to start the development server properly; it errors at the root, and serves the given endpoint as the root when I run it from the endpoint's directory. Neither of these behaviors are desirable.

[ap0nia]

• colors: I just wanted to use all the colors to see what they looked like lol. They were definitely very goofy!

• interactivity: valid; a working CLI is a better priority.

• env: sure, that stuff is configurable anyways.

• Oh, that's actually how I programmed the dev server; it'll spin up an express server for the particular endpoint with the handler responding to requests to the root. It's just a really quick way to test your own endpoint individually. I haven't configured it to be able to run at the root. To run at the root, ESBuild needs to run on every endpoint individually, watch all the subprojects, and properly assign routes to all the handlers whenever it reloads. I think it's a lot of stuff, do you think it's high priority for this tool?

[ecxyzzy]

This would definitely be high priority, since the GraphQL endpoint depends on all of the other endpoints. So while it's fine for every other endpoint to be tested individually this way, we wouldn't be able to test the GraphQL endpoint at all, apart from requesting a staging deployment and testing it from there.