Websocket server should be handling the path `/session` instead of `/command`

[gnarf]

https://w3c.github.io/at-driver/#transport specifies:

When a client establishes a WebSocket connection connection by connecting to one of the set of active listeners listener, the implementation must proceed according to the WebSocket server-side requirements, with the following steps run when deciding whether to accept the incoming connection:

1. Let resource name be the resource name from reading the client’s opening handshake. If resource name is not "/session", then stop running these steps and act as if the requested service is not available.

2. Run any other implementation-defined steps to decide if the connection should be accepted, and if it is not stop running these steps and act as if the requested service is not available.

3. Add the connection to the set of WebSocket connections not associated with a session.

This isn't blocking anything on my end however, I just made this a configurable URL, but I thought you might like to update to be in line with the latest in the spec.