Add failing test for migrating mockwebserver code

[busches]

What's changed?

Opening a draft PR to see if the migration in the test here is something that OpenRewrite can do and wants to take on. If yes, I'm happy to take it on and would love a point in the right direction.

What's your motivation?

Right now when running the UseWiremockExtension recipe you're often left with code that requires manual updates and I'd love to automate that away.

Anything in particular you'd like reviewers to focus on?

Is this something OpenRewrite wants to take on?

Anyone you would like to review specifically?

N/A

Have you considered any alternatives or workarounds?

Manual updates

Any additional context

Nope

Checklist

• I've added unit tests to cover both positive and negative cases
• I've read and applied the recipe conventions and best practices
• I've used the IntelliJ IDEA auto-formatter on affected files

[timtebeek]

hi @busches ; I'd missed this PR as it's marked as draft, and I don't get notified for new drafts unless mentioned or marked as ready for review. Sorry about that!

That said there is some good news as well: last week we've revised how we migrate mockwebserver3:

• Correcting MockWebServer migration for OkHttp #849

I hope that solves the issues you were seeing. Would you mind double checking? I'l optimistically close this PR, but we can reopen if there's still work to do (and the conflicts are resolved).

[busches]

Hi @timtebeek that PR looks great! I opened this draft PR as that's how I read the Contributing Guide, but I see now I should have also opened an issue, that's my mistake! I think most of our Boot 3.5 migration is done, but if I run into anything else, I'll be back, thanks!

[timtebeek]

All good, thanks for helping out, and sounds like the recipes have helped your there. Glad to hear!