Related to #29575, we need to phase out JettyWebSocketClient since it is tied to Jetty 11 and not worth upgrading to the relocated client API in Jetty 12, effectively superseded by the Jakarta WebSocket based StandardWebSocketClient for our purposes. Let's therefore deprecate our two JettyWebSocketClient variants in 6.0.3 already, preparing for removal in 6.1.
Related to #29575, we need to phase out
JettyWebSocketClientsince it is tied to Jetty 11 and not worth upgrading to the relocated client API in Jetty 12, effectively superseded by the Jakarta WebSocket basedStandardWebSocketClientfor our purposes. Let's therefore deprecate our twoJettyWebSocketClientvariants in 6.0.3 already, preparing for removal in 6.1.