Add direct mockwebserver3 dep when only inherited from parent pom

[steve-aom-elliott]

What

Adds an AddDependency step to the UpgradeOkHttpMockWebServer recipe so that com.squareup.okhttp3:mockwebserver3:5.x (test scope) is written into the project's own pom when the old mockwebserver artifact came in via an inherited <dependencies> block from a parent pom.

Why

ChangeDependency only operates on dependencies declared directly in the pom under refactor. When the dep was declared in a parent pom that's outside the refactor scope (a corporate parent, an external BOM, etc.), ChangeDependency has nothing to rewrite, and the project is left without any declared mockwebserver3 dependency despite still using okhttp3.mockwebserver.* types in source.

Adding AddDependency with onlyIfUsing: okhttp3.mockwebserver..* and acceptTransitive: true covers this case: if the new artifact isn't already on the classpath as direct or transitive, it's added directly to the consumer's pom.

Test

Added shouldAddDirectDependencyWhenInheritedFromExternalParent to UpgradeOkHttpMockWebServerTest. The child pom in the fixture declares <parent>com.huawei.openstack4j.connectors:openstack4j-connectors:1.0.26</parent> — a real Maven Central pom-packaged artifact that declares mockwebserver:3.2.0 (test scope) in its <dependencies> block. Since the parent isn't part of the test fixture's project, the recipe cannot modify it, mirroring the customer scenario.

The test asserts:

• The child pom gains a direct <dependency> on mockwebserver3 at 5.x with <scope>test</scope>.
• Java source import okhttp3.mockwebserver.MockWebServer is rewritten to import mockwebserver3.MockWebServer (via the existing UpdateMockWebServerMockResponse → ChangePackage step).

Marking draft because I haven't been able to run the affected tests locally due to a SNAPSHOT-drift issue in my workspace that breaks every test in this module that parses Java (a known-good sibling test fails identically). CI will be the first clean signal.