Name a ChangeDependency instance by the coordinates it changes

[jkschneider]

What's changed

ChangeDependency now implements getInstanceNameSuffix(), rendering the coordinates it acts on:

@Override
public String getInstanceNameSuffix() {
    return String.format("`%s:%s`", oldGroupId, oldArtifactId);
}

Why

The two recipes this one delegates to already do exactly this, byte for byte:

• ChangeDependencyGroupIdAndArtifactId
• org.openrewrite.gradle.ChangeDependency

So the unified recipe was the only one of the three whose instance name did not name its
coordinates, and the same logical change read differently depending on which build tool it
dispatched to.

The default Recipe.getInstanceName() interpolates an option value only when exactly one
option is required. ChangeDependency requires two (oldGroupId, oldArtifactId), so it
fell through to the bare display name and every instance came out identical:

Change Gradle or Maven dependency
Change Gradle or Maven dependency
Change Gradle or Maven dependency

That is most visible in a composite that lists several. UpgradeSpringBoot_4_0 lists seven,
and they are the starter renames that make up much of a Boot 4 migration:

old	new
spring-boot-starter-web	spring-boot-starter-webmvc
spring-boot-starter-aop	spring-boot-starter-aspectj
spring-boot-starter-oauth2-client	spring-boot-starter-security-oauth2-client
spring-boot-starter-oauth2-resource-server	spring-boot-starter-security-oauth2-resource-server
spring-boot-starter-oauth2-authorization-server	spring-boot-starter-security-oauth2-authorization-server
spring-boot-starter-web-services	spring-boot-starter-webservices
jobrunr-spring-boot-3-starter	jobrunr-spring-boot-4-starter

Instance names also surface in SourcesFileResults and RecipeRunStats, where seven
identical rows are no more useful to someone reading the data table than to someone reading
the recipe list.

After:

Change Gradle or Maven dependency `org.springframework.boot:spring-boot-starter-web`
Change Gradle or Maven dependency `org.springframework.boot:spring-boot-starter-aop`
Change Gradle or Maven dependency `org.jobrunr:jobrunr-spring-boot-3-starter`

Note on the destination coordinate

This follows the two delegates and renders only the old coordinate, which is enough to tell
instances apart. Showing old → new would read better still, but it would make this recipe
inconsistent with its delegates again, so it belongs in a change to all three rather than here.

Test plan

• ChangeDependencyTest.instanceName asserts the rendered name for the
  spring-boot-starter-web → spring-boot-starter-webmvc case
• CI — this could not be run locally: ./gradlew test fails to compile
  UpgradeTransitiveDependencyVersion against the rewrite snapshot resolved in my
  environment, in a file this PR does not touch