hotfix: revert BATCH_CONNECTION_REQUESTS default to False (#18)

PR #13 changed the default to True, but batching is broken:

1. SDK: addConnection expects an immediate response with connection_id
   and peer_id. With batching, sendConnectionEvent queues the event and
   returns undefined, causing the SDK to throw and remove the connection.

2. API: the batch endpoint (ConnectionEventBatchView) returns an empty
   200 with no connection_id or peer_id, so even if the SDK didn't
   crash, it couldn't map subsequent events to the connection.

Reverting to False (original behavior) to prevent connection monitoring
from breaking in production.

Author: Boanerges1996

api/settings.py

@@ -149,7 +149,7 @@
 # Other App defaults
 DEFAULT_INTERVAL = int(os.getenv('STATS_INTERVAL_MS', 10000))
 
-BATCH_CONNECTION_REQUESTS = os.getenv('BATCH_CONNECTION_REQUESTS', 'True').lower() == 'true'
+BATCH_CONNECTION_REQUESTS = os.getenv('BATCH_CONNECTION_REQUESTS', 'False').lower() == 'true'
 
 INIT_TOKEN_SECRET = os.getenv('INIT_TOKEN_SECRET')
 SESSION_TOKEN_SECRET = os.getenv('SESSION_TOKEN_SECRET')