Change the Jetty dependency coordinates going from EE9 to EE10

[ChenyuWang98]

What's changed?

What's your motivation?

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

Anyone you would like to review specifically?

Have you considered any alternatives or workarounds?

Any additional context

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]

Thanks for the help here @ChenyuWang98 ! When comparing the Java EE 9 and 10 recipes I noticed that we're matching the "old" identifiers before the Java EE 9 upgrade in the EE 10 upgrade, but those will already have been changed, since Java EE 10 first runs org.openrewrite.java.migrate.jakarta.JavaxMigrationToJakarta, which includes org.openrewrite.java.migrate.jakarta.JettyUpgradeEE9.

[timtebeek]

Here and below I think we should expect the ee9 specific dependencies and change those to ee10.

Suggested change

	oldGroupId: org.eclipse.jetty.websocket
	oldArtifactId: websocket-server
	oldGroupId: org.eclipse.jetty.ee9.websocket
	oldArtifactId: jetty-ee9-websocket-jetty-server

[timtebeek]

Let me know if you're ok to make those adjustments; otherwise we can try to pick this up on our side.

[ChenyuWang98]

I think there's no problem. My only wish is that Jetty be upgraded to EE10 concurrently with the Jakarta EE10 upgrade.

[timtebeek]

I've made the suggested changes to fix the test. Thanks for flagging this omission!