Update query types documentation with new demos and content

- Update the subtitle and content for the "Query Types" page to focus on Sourcegraph chat instead of the omnibox
- Add new video demos for the Symbol Search, File Search, String Literal Search, and Error Lookups features
- Refine the content and examples for each query type to provide a more comprehensive overview

Author: jdorfman

docs/cody/chat/query-types.mdx

@@ -1,6 +1,6 @@
 # Query Types
 
-<p className="subtitle">This page lists the all the query types that will return search results with the Sourcegraph omnibox.</p>
+<p className="subtitle">This page lists the all the query types that will return search results with Sourcegraph chat.</p>
 
 ## Symbol Search
 
@@ -16,7 +16,9 @@ It enables developers to explore and understand symbol usage patterns through a
 
 ### Demo
 
-🔴 Waiting for UI to update 🔴
+<video width="100%" controls>
+  <source src="https://storage.googleapis.com/sourcegraph-assets/Docs/chat-query-types-symbol-search-20250124.mp4" type="video/mp4" />
+</video>
 
 ## File Search
 
@@ -29,41 +31,38 @@ This two-step approach is particularly powerful when you need to analyze pattern
 ### Try it
 
 1. Type `package.json`
-2. Above the results, you will find the message "Query review selected a code search response."
+2. Check the checkbox next to the results you want to analyze
 3. Follow up with `List all the dependencies used across these package.json files`
 
 ### Demo
 
-🔴 Draft, replace with final version and upload to GCP 🔴
-
 <video width="100%" controls>
-  <source src="https://p21.p4.n0.cdn.zight.com/items/BlumxXBE/55c5afa3-dee3-4b6c-bfd9-d3802360db2f.mp4?v=ec57e9a8c8e4a3d3af88635fcaf796d7" type="video/mp4" />
+  <source src="https://storage.googleapis.com/sourcegraph-assets/Docs/chat-query-types-file-search-20250124.mp4" type="video/mp4" />
 </video>
 
 ## String Literal Search
 
 <p className="subtitle">String literal search is a query type or workflow that allows you to find exact text matches by enclosing your search term in quotes, ensuring precise matching instead of keyword-based results.</p>
 
-When you enclose text in quotes like `"// Scheme for Authorization header"` or `"unrecognized HTTP Authorization request"`, Sourcegraph performs an exact match search rather than keyword matching. After finding relevant files, you can select specific ones to analyze and ask follow-up questions about their contents - creating an interactive workflow that combines precise search with contextual code analysis.
-
-🔴 Temp image 🔴
-![](https://p21.p4.n0.cdn.zight.com/items/8LuW5obg/895c40c8-82ff-4f42-ab21-c500ab3ce0d5.png?v=23fd39830504212ba80e2f51a31a0a4b)
+When you enclose text in quotes like `""authInfo: async provider =>""`, Sourcegraph performs an exact match search rather than keyword matching. After finding relevant files, you can select specific ones to analyze and ask follow-up questions about their contents - creating an interactive workflow that combines precise search with contextual code analysis.
 
-### Try it out
+### Try it
 
-1. Start a new chat with `"// Scheme for Authorization header"`
+1. Start a new chat with `"authInfo: async provider =>"`
 2. Select a subset of the search results which include usage for the string
 3. Follow up with `Summarize the contents`
 
 ### Demo
 
-🔴 Video coming soon 🔴
+<video width="100%" controls>
+  <source src="https://storage.googleapis.com/sourcegraph-assets/Docs/chat-query-types-string-literal-search-20250124.mp4" type="video/mp4" />
+</video>
 
 ## Error Lookups
 
-<p className="subtitle">Error Lookups is a conversational workflow for the Sourcegraph omnibox that helps developers understand error messages by providing plain-English explanations of when and why specific errors occur in their codebase and external service calls.</p>
+<p className="subtitle">Error Lookups is a conversational workflow for Sourcegraph chat that helps developers understand error messages by providing plain-English explanations of when and why specific errors occur in their codebase and external service calls.</p>
 
-Developers can use Error Lookups to understand error messages occurring in their codebase. When encountering an error, especially from external services or dependencies, developers can use the omnibox to:
+Developers can use Error Lookups to understand error messages occurring in their codebase. When encountering an error, especially from external services or dependencies, developers can use chat to:
 
 1. Search for specific error messages across their codebase
 2. Select relevant files where the error is thrown or handled
@@ -80,14 +79,12 @@ This approach helps developers make more informed decisions about error handling
 
 ### Try it
 
-* Query for `"unsupported value for type filter"`
+* Query for `"unsupported platform"`
 * Select the file(s) where the error is thrown
 * Follow up with "Explain when and why this error is thrown"
 
 ### Demo
 
-🔴 Upload video to GCP 🔴
-
 <video width="100%" controls>
-  <source src="https://p21.p4.n0.cdn.zight.com/items/QwuyA4q7/dda31e22-d3ba-4844-b1d5-95978f2a7b1f.mp4?v=75789259e408c85fa268aa105c974894" type="video/mp4" />
+  <source src="https://storage.googleapis.com/sourcegraph-assets/Docs/chat-query-types-error-lookups-20250124.mp4" type="video/mp4" />
 </video>