revert: correct commit used for snyk-ls

[rrama]

Pull Request Submission Checklist

• Follows CONTRIBUTING guidelines
• Commit messages
  are release-note ready, emphasizing
  what was changed, not how.
• Includes detailed description of changes
• Contains risk assessment (Low | Medium | High)
• Highlights breaking API changes (if applicable)
• Links to automated tests covering new functionality
• Includes manual testing instructions (if necessary)
• Updates relevant GitBook documentation (PR link: ___)
• Includes product update to be announced in the next stable release notes

What does this PR do?

The snyk-ls commit was pointing to a commit on a feature branch, not main.
This happened in #6766.
This commit reverts back to the previous snyk-ls commit CLI was using.

Refs: 36ff328

Where should the reviewer start?

How should this be manually tested?

What's the product update that needs to be communicated to CLI users?

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[rrama]

May need test/jest/acceptance/language-server-extension.spec.ts reverting to the previous version of the file (use the version at 5927337).
Edit: I did need to do this, so I have done it.

[snyk-pr-review-bot]

PR Reviewer Guide 🔍

🧪 PR contains tests

🔒 No security concerns identified

⚡ No major issues detected

📚 Repository Context Analyzed This review considered 4 relevant code sections from 4 files (average relevance: 1.00) release-scripts/write-ls-protocol-version.go (lines 1-298) package.json (lines 1-224) package-lock.json (lines 6-275) scripts/upgrade-snyk-go-dependencies.go (lines 1-135)