[I] Replace dropwizard-websockets with Jakarta WebSocket on Jetty 11 [texera]

["Yicong-Huang (via GitHub)" <gi...@apache.org>]

Yicong-Huang opened a new issue, #5425:
URL: https://github.com/apache/texera/issues/5425

   ### Task Summary
   
   `amber/build.sbt` depends on `com.liveperson:dropwizard-websockets:1.3.14` (last release 2018, Dropwizard 1.3.x only). The five amber WebSocket sites it powers:
   
   - `amber/src/main/scala/org/apache/texera/web/resource/WorkflowWebsocketResource.scala`
   - `amber/src/main/scala/org/apache/texera/web/resource/CollaborationResource.scala`
   - `amber/src/main/scala/org/apache/texera/web/resource/pythonvirtualenvironment/PveWebsocketResource.scala`
   - `amber/src/main/scala/org/apache/texera/web/resource/WebsocketPayloadSizeTuner.scala`
   - `amber/src/main/scala/org/apache/texera/web/ServletAwareConfigurator.scala`
   
   The resource classes use `@javax.websocket.server.ServerEndpoint` (JSR-356). Under Dropwizard 4 the equivalent annotation is `@jakarta.websocket.server.ServerEndpoint` and the runtime container moves from Jetty 9's Jakarta-flavoured WebSocket support to Jetty 11's `JakartaWebSocketServletContainerInitializer`. There is no Dropwizard-4-compatible build of `dropwizard-websockets`, so the bundle registration code in `TexeraWebApplication` and `ComputingUnitMaster` must be replaced with manual container wiring.
   
   Part of #5423. Highest-risk sub-issue: collaborative editing and live workflow execution depend on these endpoints.
   
   ### Task Type
   
   - [x] Refactor / Cleanup


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org