Prevent SAST groovy analyzer from analyzing jars with dependencies
Problem to solve
Currently the SAST groovy analyzer scans both classes and jars in the build/ directory. If the jars contain the dependencies, that means that the analysis will take much longer, and I'm not sure we should be presenting security issues that are present in the dependencies.
Proposal
Prevent SAST groovy analyzer from analyzing jars with dependencies