Allow for Custom WSS Endpoint in Jupiter Terminal Widget

[cereum]

Description

The Jupiter Terminal Widget currently allows users to set a custom RPC endpoint. However, there is an issue when using session-based authentication on Vercel to secure the endpoint. We have a session-based authenticated websocket endpoint, but the terminal interface only accepts a single endpoint for both HTTP and WSS requests.

Due to using an API route, it is not possible to handle websockets in the same place as the RPC endpoint. This limitation prevents us from properly configuring the authentication for our specific setup.

Proposed Solution

To address this issue, we suggest modifying the Jupiter Terminal Widget to allow users to specify separate endpoints for HTTP and WSS requests. This enhancement would align with the connection configuration exposed by @solana/web3.js and provide more flexibility for users with custom authentication requirements.

The proposed changes would include:

1. Updating the widget's configuration options to accept two separate endpoints:

• endpoint: The HTTP endpoint for RPC requests.
• wsEndpoint (optional): The WSS endpoint for websocket connections.

2. Modifying the internal logic of the widget to use the specified wsEndpoint (if provided) for establishing websocket connections, while continuing to use the endpoint for regular HTTP requests.
3. Updating the widget's documentation and examples to reflect the new configuration options and their usage.

By implementing this enhancement, users will have the flexibility to configure the Jupiter Terminal Widget to work seamlessly with their session-based authenticated websocket endpoints on Vercel or other hosting platforms.

[worlddlckgh]

Hi, we have this PR that I hope would be useful,
#87