Follow-up from "Use Duo Chat for explain code feature"
<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=439978) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=439978) </details> <!--IssueSummary end--> ### Summary This is a follow-up from !143217 to pass `contentAboveCursor` and `contentBelowCursor` in the GraphQL mutation when using the Explain Code feature. This should put is closer to how explain code works in VSCode. The following discussion from !143217 should be addressed: - [ ] @dmishunov started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/143217#note_1751744180): > **note:** The `chat` action also accepts `contentAboveCursor` and `contentBelowCursor` as part of the `currentFile`prop as defined in https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/app/graphql/types/ai/current_file_input_type.rb. Do we plan on including those as well to have the feature 100% identical to `/explain` in VSCode?
issue