TS SDK Setup

[sodic]

Notes for reviewers

You can ignore the todos (they're mostly notes for me and I'll soon be moving them somewhere else).
You can comment on them if you want, but it isn't necessary.

The wasp ts-setup command is unfinished (more on that below). We can discuss how functional it has to be before the release.

Context

This PR is complementary to #2276.

It contains the changes that enable the user to create and work in a TS SDK project that looks like this:

├── main.wasp.mts         // Wasp config file
├── package.json
├── package-lock.json
├── public
├── schema.prisma
├── src
├── tsconfig.src.json     // tsconfig for src
├── tsconfig.json         // Composite  tsconfig
├── tsconfig.wasp.json    // tsconfig for the Wasp config file
├── vite.config.ts
└── node_moduels
    ├── ...
    └── wasp-config       // The package for the TS sdk

Those changes include:

1. The wasp-config packages that servers as an API for both our users and waspc.
2. A wasp ts-setup command that sets up the project to work with a config in TypeScript (TS SDK).

It's just the blue parts from this graph plus the prep work necessary for making the whole thing functional. The idea is to review this PR by treating the purple parts as a black box (that part is covered in #2276).

[Martinsos]

Ok, did a quick shallow review, let's take of stuff that is important for release, and the rest we can do after it!

For release, what I think is most important is two comments:

1. How easy it is for them to set up the project to be able to use TS SDK. Existing or new project.
2. Is it ok that we pollute their package.json with mention of wasp-config package, and that we have that in our basic template.