fix: panic in extractKey

[officialasishkumar]

Fixes a panic in the extractKey function by adding proper bounds checking and improving key extraction logic. The fix addresses the issue where accessing string indices without length validation could cause out-of-bounds panics.

• Adds bounds checking before accessing string indices to prevent panics
• Refactors key extraction logic to be more robust with edge cases
• Introduces a helper function unquoteKey for consistent key cleaning

[keploy]

To generate Unit Tests for this PR, please click here.

[Copilot]

Pull Request Overview

Fixes a panic in the extractKey function by adding proper bounds checking and improving key extraction logic. The fix addresses the issue where accessing string indices without length validation could cause out-of-bounds panics.

• Adds bounds checking before accessing string indices to prevent panics
• Refactors key extraction logic to be more robust with edge cases
• Introduces a helper function unquoteKey for consistent key cleaning

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

This line can still cause a panic if line is an empty string after trimming. The empty string check should be performed before accessing line[0].

Suggested change

	if line[0] == '-' || line[0] == '+' {
	if len(line) > 0 && (line[0] == '-' || line[0] == '+') {

[officialasishkumar]

good to have but this will never happen since line 223 handles that

[Copilot]

[nitpick] There's an unnecessary empty line that breaks the consistency of the switch statement formatting.

Suggested change

expectMap = map[string]interface{}{cleanExpectKey: jsonObj}