fix: two high sev vulns in the aws-sdk-go-v2 deps

[j-luong]

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?

Fixes two vulns in the CLI:

• https://security.snyk.io/vuln/SNYK-GOLANG-GITHUBCOMAWSAWSSDKGOV2AWSPROTOCOLEVENTSTREAM-16316402
• https://security.snyk.io/vuln/SNYK-GOLANG-GITHUBCOMAWSAWSSDKGOV2SERVICES3-16316411

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.

[snyk-pr-review-bot]

PR Reviewer Guide 🔍

🧪 No relevant tests

🔒 No security concerns identified

⚡ No major issues detected

📚 Repository Context Analyzed This review considered 12 relevant code sections from 8 files (average relevance: 0.73) scripts/upgrade-snyk-go-dependencies.go (lines 1-135) CONTRIBUTING.md (4 segments, lines 301-400) dangerfile.js (lines 1-100) help/cli-commands/ignore.md (lines 201-204) README.md (2 segments, lines 101-131) help/README.md (lines 1-19) help/_about-this-project/README.md (lines 1-5) ... and 1 more file(s)