Remove limit violation filter from security analysis SPI

[sylvlecl]

• Do you want to request a feature or report a bug?

Removal of obsolete component.

• What is the current behavior?

The security analysis providers are expected to take into account a LimitViolationFilter which can remove some violations from the result.

I would propose to remove that parameter from the SPI because:

• its behaviour can, and probably should, be implemented as post processing of the result
• it's redundant with the violation detector (which design and presence in the SPI is also questionable, indeed)

This is a proposition, to be discussed.

[geofjamg]

Ok, I would also remove the violation detector from SPI as it is impl related