feat(code search): Use filenames and line numbers (#28)

* Parse filename and linenumber correctly for both JSON and REGEX parsers

* Revert changes made to LogTreeItem

* Handle bad regex patterns

* Update JSON parse to parse entire file over line by line parsing

* Improve search term cleaning

* Handle corner case when there is no path to the file name

* Bump up version

Author: priyankc

package-lock.json

@@ -2,7 +2,7 @@
   "name": "traceback",
   "displayName": "TraceBack",
   "description": "A VS Code extension that brings telemetry data (traces, logs, and metrics) into your code.",
-  "version": "0.4.13",
+  "version": "0.4.14",
   "publisher": "hyperdrive-eng",
   "repository": {
     "type": "git",

package.json

@@ -433,6 +433,14 @@ Use the analyze_callers function to return the results in the exact format requi
                                             type: "string",
                                             description: "Capture group name for service name"
                                         },
+                                        fileName: {
+                                            type: "string",
+                                            description: "Capture group name for source file name"
+                                        },
+                                        lineNumber: {
+                                            type: "string",
+                                            description: "Capture group name for source line number"
+                                        }
                                     },
                                     additionalProperties: true
                                 }
@@ -452,6 +460,15 @@ Use the analyze_callers function to return the results in the exact format requi
 3. Variables - values shown in the log (e.g., "user_id=123") - if present
 4. Timestamp - in any format - if present
 5. Service name or component - if present
+6. File name - source file where the log originated - if present
+7. Line number - source line number in the file - if present
+
+Pay special attention to file names and line numbers which might appear in formats like:
+- at fileName:lineNumber
+- in fileName line lineNumber
+- fileName(lineNumber)
+- [fileName:lineNumber]
+- fileName.ext:lineNumber
 
 Log samples:
 ${selectedSamples.map((sample, i) => `${i+1}. ${sample}`).join('\n')}`;
@@ -482,8 +499,16 @@ The pattern should be comprehensive enough to extract:
 - timestamp: The timestamp in any format, if present
 - message: The main log message content
 - serviceName: The name of the service or component generating the log
+- fileName: The source file name if present (with or without extension)
+- lineNumber: The line number in the source file if present
 - Any other relevant fields
 
+For file names and line numbers, ensure the patterns can handle:
+- Various delimiters between file name and line number (:, line, at line, etc.)
+- File names with or without extensions
+- File paths (partial or full)
+- Line numbers in different formats (parentheses, brackets, after "line", etc.)
+
 Ensure the regex patterns:
 - Are compatible with JavaScript's regular expression engine
 - Use named capture groups for all extracted fields