AddDependency: tests showing version update inconsistency with test sources

[Jenson3210]

Summary

• Fixes AddDependency: version update skipped when only test sources are present #6962

AddDependency with onlyIfUsing=null did not update an existing dependency's version when only test sources were present. This happened because:

1. The compile scope check (lines 228-239) found the dependency at a different version and fell through (correct)
2. The test/provided scope check (lines 243-250) then matched on groupId + artifactId without checking the version, causing an early return that skipped the update
3. Even if the test/provided check was bypassed, AddDependencyVisitor would block the change as a "scope reduction" (compile → test)

Fix

• The compile scope check now handles version updates directly when the dependency is direct and the recipe scope is unspecified or compile, calling AddDependencyVisitor with compile scope
• When the recipe explicitly requests a narrower scope (e.g. runtime), the existing behavior is preserved: the compile-scope dep is considered sufficient
• The test/provided scope check now includes a version comparison, matching the compile scope check behavior, for dependencies exclusively in those scopes

Test plan

• existingDependencyUpdatedWithMainSources — compile scope, version bumps from 29.0-jre → 30.0-jre
• existingDependencyUpdatedWithTestSourcesOnly — test scope (only srcTestJava), version now correctly bumps from 29.0-jre → 30.0-jre
• All 49 existing AddDependencyTest cases pass, including addDependencyDoesntAddWhenExistingDependencyWithBroaderScope (explicit scope="runtime" with compile dep — no changes)