feat: implemented background requests

[nickytonline]

This pull request introduces significant updates to the codebase, primarily focusing on integrating background job management functionality, and enhancing the architecture for better state management and usability.

For testing out background mode, I've been using this prompt with o3 "Research and summarize the key differences between the top three open-source vector database solutions (such as Milvus, Qdrant, and Weaviate), including their architecture, supported features, scalability, and real-world use cases. Then, recommend the most suitable option for a SaaS platform handling millions of embeddings per day, justifying your choice."

const BACKGROUND_SUPPORTED_MODELS = [
  'gpt-4o',
  'gpt-4.1',
  'gpt-4.1-mini',
  'gpt-4.1-nano',
  'o3',
  'o4-mini',
]

Closes #71

CleanShot.2025-07-22.at.18.04.40.mp4

[netlify]

✅ Deploy Preview for mcp-storybook ready!

Name	Link
🔨 Latest commit	e9599d4
🔍 Latest deploy log	https://app.netlify.com/projects/mcp-storybook/deploys/6883d7829981fd00086dd265
😎 Deploy Preview	https://deploy-preview-160--mcp-storybook.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[nickytonline]

One thing I noticed with this feature @wasaga, is once the background job has streamed in, whether that's just letting it all stream in initially, or loading it from the background jobs sidebar is subsequent prompts start a new background job. I think after the initial job, we can unset the background toggle, so the conversation continues. If we do that though, you'd have the oroginal background job that finished before that new prompt, and a new conversation that just continues where the original one ended. I think this is fine for the moment since we have no real storage atm. Thoughts?