fix(FP): Several FPs not suitable for our automation

[aikebah]

Fixed Issues: see the linked tickets

Description of Change

FP suppressions for which either the automation could not run, or the automation yields an inappropriate suppression

Have test cases been added to cover the new functionality?

no

[aikebah]

@jeremylong given the amount of libraries hit by #5502 I think it would be good to get an 8.1.1 release out when this PR is integrated

[adam-siklosi]

Hi @aikebah

When I saw the release notes for #4723 I thought the age of updating DependencyCheck version for false positive suppressions is over.
Was that a misunderstanding from my side or you are still working on some aspect of this feature?

Thanks!
Adam

[aikebah]

@adam-siklosi Not all suppressions are feasible for the automation. The automation is allowing most suppressions (the simple ones - single library, improper CPE - which is the majority of the FP reports) to have a much faster roundtrip time without a need to release (simple suppressions for one library can be handled by automation to be pushed to the published suppressions).
The more complex ones are still only processed in regular development. There is no automation in place to process manual additions to published suppressions.

[jeremylong]

@aikebah I'll release the new version shortly.

[Marcono1234]

@aikebah, in cases where automation cannot create the suppression, would it not be possible to create the pull request manually against the generatedSuppressions branch (or manually edit the bot generated suppression as it was done in #5122 (comment))?