fix(websocket): Fix race conditions and memory leak

- Add state check in abort_connection to prevent double-close
- Fix memory leak: free errormsg_buffer on disconnect
- Reset connection state on reconnect to prevent stale data
- Implement lock ordering for separate TX lock mode
- Added sdkconfig.ci.tx_lock config

Author: surengab

components/esp_websocket_client/esp_websocket_client.c

@@ -1076,9 +1076,9 @@ static esp_err_t esp_websocket_client_recv(esp_websocket_client_handle_t client)
 
         xSemaphoreGiveRecursive(client->lock);  // Release client->lock
 
-        // Now acquire tx_lock (safe - no circular wait possible)
-        if (xSemaphoreTakeRecursive(client->tx_lock, portMAX_DELAY) != pdPASS) {
-            ESP_LOGE(TAG, "Failed to acquire tx_lock for PONG");
+        // Now acquire tx_lock with timeout (consistent with PING/CLOSE handling)
+        if (xSemaphoreTakeRecursive(client->tx_lock, WEBSOCKET_TX_LOCK_TIMEOUT_MS) != pdPASS) {
+            ESP_LOGE(TAG, "Could not lock ws-client within %d timeout for PONG", WEBSOCKET_TX_LOCK_TIMEOUT_MS);
             xSemaphoreTakeRecursive(client->lock, portMAX_DELAY);  // Re-acquire client->lock before returning
             return ESP_OK;  // Return gracefully, caller expects client->lock to be held
         }