Adopt new MockWebServer Maven coordinate and package name

[timtebeek]

What problem are you trying to solve?

Version 5.0.0-alpha.2 changes the MockWebServer Maven coordinate and package name.

In this release MockWebServer has a new Maven coordinate and package name. A longstanding problem with MockWebServer has been its API dependency on JUnit 4. We’ve reorganized things to remove that dependency while preserving backwards compatibility.

Maven Coordinate	Package Name	Description
com.squareup.okhttp3:mockwebserver3:5.0.0-alpha.2	mockwebserver3	Core module. No JUnit dependency!
com.squareup.okhttp3:mockwebserver3-junit4:5.0.0-alpha.2	mockwebserver3.junit4	Optional JUnit 4 integration.
com.squareup.okhttp3:mockwebserver3-junit5:5.0.0-alpha.2	mockwebserver3.junit5	Optional JUnit 5 integration.
com.squareup.okhttp3:mockwebserver:5.0.0-alpha.2	okhttp3.mockwebserver	Obsolete. Depends on JUnit 4.

What precondition(s) should be checked before applying this recipe?

None.

Describe the situation before applying the recipe

Old dependency & package in use.

Describe the situation after applying the recipe

Dependency & package updated.

Have you considered any alternatives or workarounds?

Not really

Any additional context

Source: https://square.github.io/okhttp/changelogs/changelog/#version-500-alpha2

For the implementation we could likely reuse these existing recipes configured through Yaml:
https://docs.openrewrite.org/recipes/java/changepackage
https://docs.openrewrite.org/recipes/java/dependencies/changedependency

That way at most we'll need some tests if we want to be sure we correctly replace these, but no code otherwise.