Perform same newGroupId and newArtifactId validations for Gradle ChangeDependency recipe

[shanman190]

What's changed?

Added same validation for Gradle ChangeDependency as was done for the Maven equivalent via #3889.

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

I did go ahead and clean up the descriptions a little bit more, so now I think they overall are a bit clearer in terms of intent.

Have you considered any alternatives or workarounds?

N/A

Any additional context

• Validate that Change(Managed)DependencyGroupIdAndArtifactId updates GAV #3889
• 82d57a4

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

[timtebeek]

Thanks! One step closer to

• Add validation to ChangeDependency, so it checks that either group or artifact is different from the old. rewrite-java-dependencies#55