In Spring Framework 7.x.x ReactorNettyWebSocketClient correctly applies maxFramePayloadLength to the underlying HttpClient, but it fails to propagate this value to the created ReactorNettyWebSocketSession.

Steps to Reproduce:

1. Configure ReactorNettyWebSocketClient with a WebsocketClientSpec that has maxFramePayloadLength set to 128KB.
2. Connect to a server (e.g., Tomcat or Jetty) that sends a frame larger than 64KB.
3. The client throws io.netty.handler.codec.TooLongFrameException: content length exceeded 65536 bytes.

The ReactorNettyWebSocketSession should respect the maxFramePayloadLength configured in the client's WebsocketClientSpec, but the session remains initialized with the default 64KB limit, causing errors when receiving larger frames.