chore: bump cli-extension-iac-rules to fix vulnerabilities [IAC-3524]

[alexandru-manea-snyk]

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?

This PR bumps cli-extension-iac-rules to the latest version to pull in a fix for multiple vulnerabilities in its dependencies.

Where should the reviewer start?

• [chore: update packages and go version to fix vulns IAC-3524 #64](chore: update go.opentelemetry.io/otel to v1.45.0 to fix vulns [IAC-3524] cli-extension-iac-rules#64)

How should this be manually tested?

Do a custom build of CLI and run an IaC scan to confirm no regressions:

make build
./binary-releases/snyk-macos-arm64 iac test .

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

N/A

Risk assessment (Low | Medium | High)?

Low - only a package update

Any background context you want to provide?

What are the relevant tickets?

• IAC-3524

Screenshots (if appropriate)

N/A

[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 🔍

🧪 PR contains tests

🔒 No security concerns identified

⚡ No major issues detected

📚 Repository Context Analyzed This review considered 30 relevant code sections from 10 files (average relevance: 0.76) scripts/upgrade-snyk-go-dependencies.go (lines 1-149) CLAUDE.md (3 segments, lines 229-315) package-lock.json (3 segments, lines 6-266) package.json (lines 1-236) cliv2-private/cmd/cliv2/main.go (lines 1-24) release-scripts/write-ls-protocol-version.go (lines 1-298) cliv2/scripts/prepare_licenses.go (lines 1-197) ... and 3 more file(s)

🤖 Repository instructions applied (from AGENTS.md)