Design: End-user Static Reachability UX/UI

Static reachability is a factor of dependencies (and the relevant CVEs) which indicates that in high probability that package is in use, and therefore the risk of it is higher. From the user it is a binary indicator of yes/no - Reachable/not Reachable.

This issue tracks UX work to support showing Static Reachability Data in the GitLab Platform. Please see the parent epic, &14177 (closed) to better understand this project.

We will need UX support to show Static Reachability data in the following areas:

1. Vulnerability report table - show an indicator that designated Reachable
2. Vulnerability report, vulnerability details page - add a badge or indicator that states Reachable: Yes or Not Available (see screenshot below for proposed placement on page
3. Vulnerability report filter - Reachable || Yes or Not Available

Note: for cases where something is not reachable we do not need to show this as it will be information overload. The user can assume that anything not labeled Reachable is unreachable. Though I would welcome feedback on this thought from Design.