Only allow Gradle AddDependency to add dependencies to the top-level dependencies block

[shanman190]

What's changed?

Due to the Groovy compiler misinterpreting receiver classes for the dependencies block, this can result in the gradle.AddDependency recipe placing new dependencies improperly.

What's your motivation?

• Fixing add gradle dependency when using spring boot dependency management #4094

Anything in particular you'd like reviewers to focus on?

Just the pattern of using a Predicate from the recipe standpoint as the mechanism with which to invert the control flow and allow more specific insertion points from a dependency standpoint.

Anyone you would like to review specifically?

Anybody who wants to double check the work.

Have you considered any alternatives or workarounds?

None

Any additional context

None

Checklist

• I've added unit tests to cover both positive and negative cases
• I've read and applied the recipe conventions and best practices
• I've used the IntelliJ IDEA auto-formatter on affected files