Re-include CloseUnclosedStaticMocks in Mockito1to4Migration

[steve-aom-elliott]

What's changed?

Re-enables CloseUnclosedStaticMocks inside the Mockito1to4Migration composite recipe.

What's your motivation?

• CloseUnclosedStaticMocks was added to Mockito1to4Migration in Recipe for closing unclosed static mocks #739 so users wouldn't need to seek it out separately, then commented out two days later in d1e6bbb after @timtebeek observed it injecting teardown in the wrong scope for @Nested classes — e.g. JMockitMockUpToMockitoTest.mockUpAtSetUpWithTearDownTest() (see the discussion on #739).

• CloseUnclosedStaticMocks: Handle Nested class, qualifiedclass name. #742 (merged two days after the comment-out) handled nested classes and qualified mocked-class names, fixing the underlying issue. The YAML line was never re-enabled — appears to have been an oversight rather than a remaining concern.

Verification

Locally green:

• JMockitMockUpToMockitoTest (the canary @timtebeek originally pointed at)
• CloseUnclosedStaticMocksTest
• Mockito1to3MigrationTest, Mockito1to4MigrationTest, Mockito1to5MigrationTest
• Full org.openrewrite.java.testing.mockito.* and org.openrewrite.java.testing.jmockit.* packages
• recipeCsvValidate (both completeness and content)

Checklist

• I've added unit tests to cover both positive and negative cases (covered by existing CloseUnclosedStaticMocksTest and the composite migration tests)
• I've read and applied the recipe conventions and best practices
• I've used the IntelliJ IDEA auto-formatter on affected files

[steve-aom-elliott]

CI failure here is pre-existing on main and unrelated to this change.

• Failing test: org.openrewrite.java.testing.junit5.UpdateMockWebServerMockResponseTest.shouldMigrateMockResponseToBuilder()
• Recipe under test: UpdateMockWebServerMockResponse — has nothing to do with Mockito1to4Migration or CloseUnclosedStaticMocks.
• Repro on main with no diff applied: ./gradlew test --tests 'org.openrewrite.java.testing.junit5.UpdateMockWebServerMockResponseTest.shouldMigrateMockResponseToBuilder' → FAILED locally on main at e1cb8925.

The reason it's been green on main push runs is that Gradle's :test task is UP-TO-DATE when nothing it touches has changed — the broken assertion just never gets re-evaluated. Push runs on main complete in ~2m vs. ~10m for PR runs, which fits that pattern. This PR forced a fresh test run and surfaced the latent failure.

The expected vs. actual diff:

-    private Builder mockResponse = new MockResponse.Builder()
+    private MockResponse.Builder mockResponse = new MockResponse.Builder()

…plus removal of the import mockwebserver3.MockResponse.Builder; line. Looks like import-shortening / inner-class handling has shifted in a dependency or the recipe itself since this test was written.

Happy to file a separate issue for that test if useful — but it shouldn't block this PR.