[TT-9864] Optimize the creation/usage of AST documents

[buraksezer]

User description

PR for https://tyktech.atlassian.net/browse/TT-9864. See TykTechnologies/graphql-go-tools#431 for details.

---

PR Type

Enhancement, Dependencies

---

Description

• Added cleanup for allocated resources in the HandleReverseProxy method in internal/graphengine/engine_v2.go.
• Updated graphql-go-tools dependency version in go.mod.
• Updated checksum for graphql-go-tools dependency in go.sum.

---

Changes walkthrough 📝

	Relevant files
Enhancement	engine_v2.go Add resource cleanup in `HandleReverseProxy` method.          internal/graphengine/engine_v2.go Added cleanup for allocated resources in HandleReverseProxy method. +2/-0
Dependencies	go.mod Update `graphql-go-tools` dependency version.                        go.mod Updated graphql-go-tools dependency version. +1/-1      go.sum Update checksum for `graphql-go-tools` dependency.              go.sum Updated checksum for graphql-go-tools dependency. +2/-2

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[github-actions]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review [1-5]	2
🧪 Relevant tests	No
🔒 Security concerns	No
⚡ Key issues to review	Resource Cleanup Verification: Ensure that the defer gqlRequest.Cleanup() call effectively cleans up all necessary resources without side effects or errors.

[github-actions]

PR Code Suggestions ✨

Category	Suggestion	Score
Possible bug	Prevent potential nil pointer dereference by checking if gqlRequest is not nil before cleanup Ensure that gqlRequest is not nil before calling Cleanup() to prevent potential nil pointer dereference. internal/graphengine/engine_v2.go [243] -defer gqlRequest.Cleanup() +if gqlRequest != nil { + defer gqlRequest.Cleanup() +} Suggestion importance[1-10]: 9 Why: This suggestion addresses a potential bug where gqlRequest could be nil, leading to a nil pointer dereference when Cleanup() is called. Adding a nil check improves the robustness and stability of the code.	9

[github-actions]

API Changes

no api changes detected

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud