fix: Missing VEX status mappings for resolved_with_pedigree and false_positive

[irenaliu18]

Description of the PR

This PR addresses issue 2812, adding support for two missing CycloneDX 1.6 VEX (Vulnerability Exploitability eXchange) status values: resolved_with_pedigree and false_positive. These statuses were introduced in CycloneDX 1.5+ but were not previously handled by the GUAC parser, causing ingestion failures with the error "unknown vulnerability status".

GUAC currently fails to ingest CycloneDX 1.6 SBOMs containing the following VEX statuses:

• resolved_with_pedigree - Indicates the vulnerability has been remediated with evidence provided in component pedigree
• false_positive - Indicates the vulnerability was falsely identified or associated with the component

Unit Tests

New test cases pass:

• Test_cyclonedxParser/valid_CycloneDX_VEX_document_with_resolved_with_pedigree_status
• Test_cyclonedxParser/valid_CycloneDX_VEX_document_with_false_positive_status

go test ./pkg/ingestor/parser/cyclonedx/... -v

PR Checklist

• All commits have a Developer Certificate of Origin (DCO) -- they are generated using -s flag to git commit.
• All new changes are covered by tests
• If GraphQL schema is changed, make generate has been run
• If GraphQL schema is changed, GraphQL client updates/additions have been made
• If OpenAPI spec is changed, make generate has been run
• If ent schema is changed, make generate has been run
• If collectsub protobuf has been changed, make proto has been run
• All CI checks are passing (tests and formatting)
• All dependent PRs have already been merged

[funnelfiasco]

In addition to resolving the addition of a GitHub workflow, you will need to include a DCO signoff before this change can be approved.

[lumjjb]

Thanks for opening up this PR! Looks great with some minor comment!

[lumjjb]

Thanks for the changes, minor comment, and started the workflow for tests!

[lumjjb]

LGTM with requirement to one test for the new code path (see comment).. Thanks @irenaliu18 !

[pxp928]

LGTM! Thank You

[funnelfiasco]

Clearing my change request since the issues have been addressed and the test failures are systemic.

[lumjjb]

I'm currently checking on which CI tests are broken we should fix/ignored (#2820) to make sure to unblock this if the failures are not caused by this PR

[lumjjb]

HI @irenaliu18, i fixed some of the CI checks, can you rebase and reupload the PR? and i can run the tests again!