Support interactive project setup

When running wasp new, we can ask users how they want set up their project. For now:

• Do they want to use TypeScript (client/server/both/none)
• Do they want to use Tailwind on the client
• Do they want us to set up Git (inspired by T3)
• Do they want us to install their dependencies right away (inspired by T3)
• Do they want AGENTS.md, CLAUDE.md and some skills (came up in a user interview)

Perhaps in the future:

• Which bundler do they want to use on the client (Webpack, Parcel, etc.)
• Which module system do they want to use with Node (commonjs, esnext, etc.)
• Which frontend framework do they want (React, Vue, etc.)

This will probably require adding a Wasp config file (perhaps we can start using that for .wasproot) and therefore include compiler/AppSpec changes.

While we're at it, we should think about what we can tell our users after they run wasp new. Take a look at Next.js and T3 for inspiration.

Some ideas:

• Tell them about different commands they'll probably want to run inside the project (e.g., wasp start).
• Tell users they need to keep wasp start running in the background to get proper IDE support.