Include language server version in code suggestions (17.1 backport)

Merging into stable branches in canonical projects is reserved for GitLab patch releases https://docs.gitlab.com/ee/policy/maintenance.html#patch-releases If you're backporting a security fix, please refer to the security merge request template https://gitlab.com/gitlab-org/security/gitlab/blob/master/.gitlab/merge_request_templates/Security%20Release.md. Security backport merge requests should not be opened on the GitLab canonical project.

What does this MR do and why?

Backporting Send language server version in AI gateway requ... (!162854 (merged) - merged) to re-enable open tabs context for self-managed customers on GitLab 17.3 and later.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch.
• The MR that fixed the bug on the default branch has been deployed to GitLab.com (not applicable for documentation or spec changes).
• This MR has a severity label assigned (if applicable).
• Set the milestone of the merge request to match the target backport branch version.
• This MR has been approved by a maintainer (only one approval is required).
• Ensure the e2e:package-and-test-ee job has either succeeded or been approved by a Software Engineer in Test.

Note to the merge request author and maintainer

If you have questions about the patch release process, please:

• Refer to the patch release runbook for engineers and maintainers for guidance.
• Ask questions on the #releases Slack channel (internal only).