Move `ask-the-documents` example app in the Wasp monorepo

[infomiho]

Currently the ask-the-documents example app lives in a separate repo at https://github.com/wasp-lang/ask-the-documents. This creates maintenance overhead since we need to update it when Wasp changes, it's not covered by our CI, and it has separate deployment.

We should move it into the main Wasp repo under examples/ask-the-documents/ so that:

• It gets updated alongside other examples
• It has CI will tests like the other examples
• It can be deployed with our other examples

Rough idea on what to do:

• Copy the app code to examples/ask-the-documents/
• Add to CI configuration
• Include in deployment pipeline
• Update documentation links
• Update old repo to point to new location
• Archive the old repo

[Martinsos]

We didn't want to do it in order to reduce the number of example apps we have to maintain.
Especially since this one is a bit more involved, with using the vector database and all.

Did that change? I am still inclined to say we leave it out, in its own repo, exactly because that allows us to not update it as often and regularly as example apps that are in the Wasp monorepo.

[FranjoMindek]

There is an option of not updating it anymore and letting it work with the old version of Wasp.
Then we should remove ask-the-documents from our release process.

[infomiho]

@FranjoMindek summed it up for me - either it is useful in our release process (which I argue it is because it's close to a real-world application which enables us to catch some categories of bugs that our other examples don't) or it's not useful and we exclude it from the process. If we decide to keep it, let's make it as easy as possible to maintain it.

[cprecioso]

Done in:

• ask-the-documents: Import app into repo #3174
• ask-the-documents: Add dotenv files #3252
• ask-the-documents: Deploy to Fly #3251
• ask-the-documents: Add CI testing #3250

Left the for later:

• Complete e2e tests for ask-the-documents #3256