[#403][Fix] Start ws-kalive loop only after conn is established (@Snu…

…rppa)

Before this commit:
  `:chsk/ws-ping` loop starts before (connect-fn) is called. This means that
  if there's some delay establishing connection, the logs get needlessly
  polluted with messages:
    - "Chsk send against closed chsk." from the ws-ping send.
    - "Chsk is closed: will try reconnect" from the connection retry-fn.

After this commit:
  Only start the ws-kalive loop after connection is established.

src/taoensso/sente.cljc

@@ -1290,6 +1290,9 @@
 
                     (reset! socket_ ?socket))))))]
 
+      (reset! retry-count_ 0)
+      (connect-fn)
+
       (when-let [ms ws-kalive-ms]
         (go-loop []
           (let [udt-t0 @udt-last-comms_]
@@ -1308,8 +1311,6 @@
                   (-chsk-send! chsk [:chsk/ws-ping] {:flush? true})))
               (recur)))))
 
-      (reset! retry-count_ 0)
-      (connect-fn)
       chsk)))
 
 (defn- new-ChWebSocket [opts csrf-token]