WebTransport ignores query parameters in URL

Describe the bug
The final WebTransport URL doesn't include the query parameters from the original URL.

To Reproduce

engine.io-client 6.6.4

Client

// Connects to: https://localhost:1234/engine.io/?x=y&EIO=4&transport=polling&t=zsyh7czl 
eio("https://localhost:1234/?x=y", {transports: ["polling"]});

// Connects to: wss://localhost:1234/engine.io/?x=y&EIO=4&transport=websocket
eio("https://localhost:1234/?x=y", {transports: ["websocket"]});

// Connects to: https://localhost:1234/engine.io/
eio("https://localhost:1234/?x=y", {transports: ["webtransport"]});

Expected behavior
The WebTransport transport should preserve the query parameters in the same way other transports do.

Additional context

WebTransport currently uses createUri to construct the URL:

https://github.com/socketio/socket.io/blob/439a8f669c6788b512dd76011c4476830d67515b/packages/engine.io-client/lib/transports/webtransport.ts#L31-L34

It doesn't include the original query parameters:

https://github.com/socketio/socket.io/blob/439a8f669c6788b512dd76011c4476830d67515b/packages/engine.io-client/lib/transport.ts#L176-L185

Start by reading packages/engine.io-client/lib/transports/webtransport.ts at the linked URL construction and compare it with packages/engine.io-client/lib/transport.ts at the linked query-handling code. Reproduce the three client examples, then verify that the WebTransport URL preserves the original query parameters like the polling and websocket URLs.