Rename Vulnerability Status `Detected` to better differentiate it from Activity

Background

There's currently some confusion around the usage of Detected within the vulnerability list as it is used to refer to both the Vulnerability.status and Vulnerability.activity.

The activity is workflow-driven and updated according to events that can occur around a vulnerability (such as becoming resolved or having an attached issue).

The vulnerability status refers to a human-driven attribute: starting in a "Detected" state and manually transitioning to others such as "Confirmed".

There are issues with applying volition to the "Activity" states since those are deterministic, so "no longer detected" works well for communicated the reality: that we are no longer detecting the vulnerability.

The status of "detected", however, is closer to a default state of "untriaged". I propose we use a different term to communicate a vulnerability is still open that better differentiates the Status from Activity

Proposal

Now

1. Change Detected to Needs triage (see designs)

Next

1. Consider keeping and status:Detected for new findings (see comment)

Future

1. Consider an Open/Closed state for vulnerabilities in the future (see issue)