feat: added check for duplicated dependency

[ashakirin]

• Refs: ChangeDependencyGroupIdAndArtifactId can duplicate new dependency #4514

[timtebeek]

I wonder if in this case we should remove the old one instead. What are your thoughts on that?

Suggested change

	<dependency>
	<groupId>jakarta.activation</groupId>
	<artifactId>jakarta.activation-api</artifactId>
	<version>1.2.1</version>
	</dependency>

[ashakirin]

@timtebeek: in theory - yes, on practice: perhaps user has a good reason to keep old dependency in pom, we do not know that. I do not think that it is responsibility of the CahngeDependencyGroupIdAndArtifact to cleanup old unused dependencies. Perhaps separate recipe would be more clean solution for this case.

[timtebeek]

Same here; I think ideally we remove the duplicate, since two managed versions of the same dependency don't make much sense (to me).

Suggested change

	<dependency>
	<groupId>javax.activation</groupId>
	<artifactId>javax.activation-api</artifactId>
	<version>1.2.0</version>
	</dependency>

[ashakirin]

Do you think it should be responsibility of ChangeDependency recipe? I think it can be a bit confusing for user, if existing dependencies disappearing