Filters for vulnerability detail output

[nleach999]

Describe the problem

Some scans may initially show a large number of results until the project has been properly onboarded. This can occasionally cause some very large data outputs with data that has a potential to incorrectly introduce statistical skews during analysis.

Proposed solution

Enable the following filtering criteria with the numbered precedence for checking:

1. Filter all detail output for scans with vulnerability counts exceeding a maximum threshold
2. Filter detail output for vulnerabilities of a given result severity if the result severity exceeds a maximum threshold
3. Filter detail output for vulnerabilities of a given query severity if the query severity exceeds a maximum threshold

Additional details

By default, no filtering should be performed unless explicitly configured.