docs: update the correct path for JS client in WebSocket client README (#1890)

Co-authored-by: sagar seth <lightningsagar0@email.com>
Co-authored-by: Lukasz Gornicki <lpgornicki@gmail.com>

Author: 3 people

packages/templates/clients/websocket/javascript/README.md

@@ -7,4 +7,4 @@ You can test this template:
 4. Install with `npm install` and run test with `npm run test`
 5. Start example script that uses a client library generated by the test: `node example.js`
 
-> By default this is testing against Hoppscotch echo service. You can modify `packages/templates/clients/websocket/javascript/example.js` and change first line to `const WSClient = require('./tests/temp/snapshotTestResult/client_postman/client.js');` and run `node example.js` again. You will see example still works but now it is using a different API. This is possible since both AsyncAPI documents define the same name of operation for sending messages: `sendEchoMessage` so each client generated has the same API.
+> By default this is testing against Hoppscotch echo service. You can modify `packages/templates/clients/websocket/javascript/example.js` and change first line to `const WSClient = require('./test/temp/snapshotTestResult/client_postman/client.js');` and run `node example.js` again. You will see example still works but now it is using a different API. This is possible since both AsyncAPI documents define the same name of operation for sending messages: `sendEchoMessage` so each client generated has the same API.