Apply add dependency correctly, taking aggregating poms into account

[Laurens-W]

What's changed?

Introduce a mechanism to know which modules an aggregating pom applies to in order to prevent unnecessarily adding dependencies to aggregating poms

Anyone you would like to review specifically?

@timtebeek @sambsnyd

Any additional context

An aggregating pom could be a parent, when it's not there's no point in adding a dependency to it

Checklist

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