New Analysis State: UPDATE

### Current Behavior:

Dependency-Track v3.4.1 (and 3.5.0-SNAPHOT) offers the following Audit Analysis states:

State | Description
------------ | -------------
EXPLOITABLE |The finding is exploitable (or likely exploitable)
IN_TRIAGE | An investigation is in progress to determine if the finding is accurate and affects the project or component
FALSE_POSITIVE | The finding was identified through faulty logic or data (i.e. misidentified component or incorrect vulnerability intelligence)
NOT_AFFECTED | The finding is a true positive, but the project is not affected by the vulnerability identified
NOT_SET | Analysis of the finding has not commenced

These states do not cover the situation where auditing has been performed and it has been determined that updating the component will resolve the vulnerability.

### Proposed Behavior:

Create an additional Analysis State:

State | Description
------------ | -------------
UPDATE |This finding is a true positive and can be resolved via upgrading the version used.

Thus, in a multi-project system with (say) 1000 vulnerabilties and 200 triaged to to have status UPDATE, one has a better indication on where to start with fixing things.

Having an UPDATE status might also allow for additional "hint" functionality to be incorporated (something that I will log separately).