Change websocket ping time to 1s to improve connection resilience?
### Summary

The websocket connection drops consistently for [this user](https://discuss.streamlit.io/t/frustrated-streamlit-frontend-disconnects-from-apps-with-long-running-processes/11612). 

In `sever/server.py`, when we change this:
```
    "websocket_ping_interval": 20,  # Ping every 20s to keep WS alive.
```
...to this:
```
    "websocket_ping_interval": 1,  # Ping every 1s to keep WS alive.
```
...the problem goes away.

**Can we make this the default?**


### Steps to reproduce

We couldn't find a toy scenario to repro this :(

### Is this a regression?

Don't think so

### Debug info

- Streamlit version: 0.80.0
- Python version: (get it with `$ python --version`)
- Using Conda
- OS version:
- Browser version:

diff --git a/lib/streamlit/server/server.py b/lib/streamlit/server/server.py
index 239280790..698daa983 100644
--- a/lib/streamlit/server/server.py
+++ b/lib/streamlit/server/server.py
@@ -69,10 +69,19 @@ LOGGER = get_logger(__name__)
 
 
 TORNADO_SETTINGS = {
-    "compress_response": True,  # Gzip HTTP responses.
-    "websocket_ping_interval": 20,  # Ping every 20s to keep WS alive.
-    "websocket_ping_timeout": 30,  # Pings should be responded to within 30s.
-    "websocket_max_message_size": MESSAGE_SIZE_LIMIT,  # Up the WS size limit.
+    # Gzip HTTP responses.
+    "compress_response": True,
+    # Ping every 1s to keep WS alive.
+    # 2021.06.22: this value was previously 20s, and was causing
+    # connection instability for a small number of users. This smaller
+    # ping_interval fixes that instability.
+    # https://github.com/streamlit/streamlit/issues/3196
+    "websocket_ping_interval": 1,
+    # If we don't get a ping response within 30s, the connection
+    # is timed out.
+    "websocket_ping_timeout": 30,
+    # Set the websocket message size. The default value is too low.
+    "websocket_max_message_size": MESSAGE_SIZE_LIMIT,
 }
 
 
['lib/streamlit/server/server.py']