Add GraphQL API argument for filtering vulnerabilities by false_positive

Problem description

Currently, our GraphQL API for vulnerabilities doesn't provide a way to filter results based on the falsePositive field. While token status information can be resolved for findings, there is no way for consumers to filter vulnerabilities by falsePositive.

Proposed Solution

We need to extend our existing vulnerabilities reports GraphQL APIs to support filtering by falsePositive corresponding to the false_positive in the backend. This will allow consumers to filter vulnerabilities based on falsePositive on Secure > Vulnerability report

See !205482 (merged) as example.