Only consider specified configurations for UpgradeTransitiveDependencies created constraints

[Jenson3210]

What's changed?

In this version, the recipe will by default consider all transitive configurations to be adding constraints.
One can limit this behaviour by specifying constraints that need to be considered.
Eg. in the light of vulnerability patching, a recipe runner might only be interested in running against runtime jars.
That would be feasible by specifying both default runtime available configurations(implementation, runtimeOnly) + any manually added transitive ones.

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

This change will only have impact if a configurations list was specified. We reintroduce/combine earlier behaviour by checking for the extendsFrom + must be transitive.
Added some test cases to further explain expectations/behaviour.

Anyone you would like to review specifically?

Have you considered any alternatives or workarounds?

See #4230 for a blacklist approach

Any additional context

Our preference goes towards a whitelist approach as that list is afaik better maintainable for wide usage of plugins, custom configurations...

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

[sambsnyd]

Thanks @Jenson3210 I've merged this and closed the alternative blacklist proposal
#4230