fix: refactor finding column logic for excluded components

[rhartuv]

This PR fixes the finding display logic in the SBOM table when components are excluded.

Key changes:

• If 100% of components are excluded, the column now displays a new purple "No components analyzed" label instead of the excluded count.
• If there is a mix of excluded and analyzed components, the column now respects the existing finding priority (Vulnerable > Uncertain > Not Vulnerable) based only on the analyzed components, hiding the legacy "Excluded" label.

New label:

Before:

Jira

[vbelouso]

✅ 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.

[zvigrinberg]

Hi @rhartuv ,

Only minor comment about that.

Thanks.

[zvigrinberg]

@rhartuv This is not being used anymore, thus can be removed.

[zvigrinberg]

@rhartuv LGTM Approved