chore: ensure UFM presenter displays pending suppression status for issues

[CatalinSnyk]

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?

Updates GAF with a fix for the UFM presentation logic regarding the suppressions pending approval, which were previously not being displayed at all for the human readable output.

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.

[github-actions]

	Warnings
⚠️	"chore: ensure UFM presenter displays pending suppression status for issues" is too long. Keep the first line of your commit message under 72 characters.

Generated by 🚫 dangerJS against d2e920e

[snyk-pr-review-bot]

PR Reviewer Guide 🔍

🧪 No relevant tests

🔒 No security concerns identified

⚡ No major issues detected

📚 Repository Context Analyzed This review considered 6 relevant code sections from 4 files (average relevance: 0.80) scripts/upgrade-snyk-go-dependencies.go (lines 1-134) package-lock.json (3 segments, lines 1-100) cliv2/cmd/cliv2/main.go (lines 1-92) dangerfile.js (lines 1-111)