Match MockWebServer.shutdown() against pre-rename type

[steve-aom-elliott]

What

Changes the ChangeMethodName step in UpgradeOkHttpMockWebServer to match okhttp3.mockwebserver.MockWebServer shutdown() instead of mockwebserver3.MockWebServer shutdown().

Why

The step was placed before UpdateMockWebServerMockResponse, which internally runs ChangePackage("okhttp3.mockwebserver", "mockwebserver3", false). With the pattern targeting the post-rename type (mockwebserver3.MockWebServer), the method-call's declaring type at the time ChangeMethodName runs is still okhttp3.mockwebserver.MockWebServer — so the pattern doesn't match on the first cycle. OpenRewrite's iterative execution eventually completes the rename on a subsequent cycle, but it's an unnecessary cycle and the recipe reads in a confusing order (the pattern references a type that doesn't exist yet at that point).

Targeting the pre-rename type lets the rename happen in a single cycle: shutdown() → close() is applied while the old types are still in scope, then UpdateMockWebServerMockResponse's ChangePackage does the bulk move to mockwebserver3.* at the end. The recipeList now reads top-to-bottom as a natural pipeline of source rewrites against the old types, followed by the package rename as a final cleanup step.

Test

Added shouldRenameShutdownToCloseAlongWithPackageChange to UpgradeOkHttpMockWebServerTest. The fixture has a project with a direct mockwebserver:4.10.0 test-scope dep and a test source that imports okhttp3.mockwebserver.MockWebServer and calls server.shutdown(). After the recipe runs the source should import mockwebserver3.MockWebServer and call server.close().

Marking draft until CI confirms.