[ANE-695] gradle: check if configuration is deprecated

[jagonalez]

Overview

• PR adds support for ignoring deprecated configurations in gradle 6-7, which the gradle dependencies task does see here

• In gradle 6+, gradle introduced deprecated configurations, however including the configurations at first only induced a warning. In the gradle dependencies task, those configurations are ignored when attempting to resolve and list dependencies. This PR changes our gradle script to match what the gradle dependencies task does.

Acceptance criteria

• deprecated configurations are ignored for gradle projects in v6-7.

Testing plan

• use this repo: https://github.com/jagonalez/fossa-gradle-test (this repo is using a maven plugin which has dependencies in an ignored configuration).
• build the project
• cabal build fossa
• run cabal run fossa -- analyze ~/dev/fossa-gradle-test -o | jq ".projects[0].graph.deps | length"
• you should get 33 (these are the same as what is reported from gradlew dependencies
• on the master branch we're getting 38 deps

Risks

• should be minimal

Metrics

Is this change something that can or should be tracked? If so, can we do it today? And how? If its easy, do it

References

Add links to any referenced GitHub issues, Zendesk tickets, Jira tickets, Slack threads, etc.

Example:

• ANE-695

Checklist

• [x] I added tests for this PR's change (or explained in the PR description why tests don't make sense).
• [x] If this PR introduced a user-visible change, I added documentation into docs/.
• [x] If this PR added docs, I added links as appropriate to the user manual's ToC in docs/README.ms and gave consideration to how discoverable or not my documentation is.
• [x] If this change is externally visible, I updated Changelog.md. If this PR did not mark a release, I added my changes into an # Unreleased section at the top.
• [x] If I made changes to .fossa.yml or fossa-deps.{json.yml}, I updated docs/references/files/*.schema.json AND I have updated example files used by fossa init command. You may also need to update these if you have added/removed new dependency type (e.g. pip) or analysis target type (e.g. poetry).
• [x] If I made changes to a subcommand's options, I updated docs/references/subcommands/<subcommand>.md.

[jagonalez]

I know you linked to some Gradle code, but I'm not sure how that relates to specifically what we're doing.

The code I linked is for how Gradle reports dependencies when running gradle dependencies. In Gradle 6 - 7, gradle deprecated configurations: https://docs.gradle.org/current/userguide/declaring_dependencies.html#sec:deprecated-configurations.

If you compare gradle dependencies vs the fossa-cli output when a gradle project has a deprecated config - we are reporting more dependenices than gradle dependencies. IMO we should be reporting the same dependencies that gradle does.