Combining Search and Chat Backend

[yuhongsun96]

Description

• Combining Search and Chat flows
• Removing one off logic for the old one-shot flows
• Cleaning up dead code
• Restructuring repo for extending it with agent style functionality
• Cleaner abstractions and function layouts

How Has This Been Tested?

Needs significant testing across all major flows.

Accepted Risk (provide if relevant)

• Search queries receive a name in chat history only after user clicks on it.
• Very minor changes to APIs not used by frontend, may need to give a few users heads up

Related Issue(s) (provide if relevant)

N/A

Mental Checklist:

• All of the automated tests pass
• All PR comments are addressed and marked resolved
• If there are migrations, they have been rebased to latest main
• If there are new dependencies, they are added to the requirements
• If there are new environment variables, they are added to all of the deployment methods
• If there are new APIs that don't require auth, they are added to PUBLIC_ENDPOINT_SPECS
• Docker images build and basic functionalities work
• Author has done a final read through of the PR right before merge

Backporting (check the box to trigger backport action)

Note: You have to check that the action passes, otherwise resolve the conflicts manually and tag the patches.

• This PR should be backported (make sure to check that the backport attempt succeeds)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
internal-search	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 3, 2024 10:13pm

[yuhongsun96]

Could you add in this one? It should be pretty easy based on the rest of the PR

[hagen-danswer]

should probably uncomment out that test!