chore: disable snyk vuln ticket generation

[himanshusinghs]

Description

As a sideeffect of Snyk now actually scanning project code (#1136) we have bumped into yet another issue. This time its about sbom tools not able to create vuln tickets.

Because we need to rollout a fix for #1149, I am disabling snyk temporarily with a todo ticket - VSCODE-706

Checklist

• New tests and/or benchmarks are included
• Documentation is changed or added
• I have signed the MongoDB Contributor License Agreement (https://www.mongodb.com/legal/contributor-agreement)

Motivation and Context

• Bugfix
• New feature
• Dependency update
• Misc

Open Questions

Dependents

Types of changes

• Backport Needed
• Patch (non-breaking change which fixes an issue)
• Minor (non-breaking change which adds functionality)
• Major (fix or feature that would cause existing functionality to change)

[Copilot]

Pull Request Overview

This PR temporarily disables Snyk vulnerability ticket generation and vulnerability reporting in the GitHub Actions workflow to address issues with SBOM tools creating vulnerability tickets. The change is documented with a TODO ticket (VSCODE-706) for future resolution.

• Commented out the "Create Jira Tickets" step that generates vulnerability tickets
• Commented out the "Generate Vulnerability Report" step that fails on high-severity vulnerabilities
• Added a TODO comment referencing the tracking ticket VSCODE-706

---

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