Make Electrum connection logs less spammy (#571)

Stacktraces have little usefulness and are quite spammy.

Author: ebonyschneider462359

src/commonMain/kotlin/fr/acinq/lightning/blockchain/electrum/ElectrumClient.kt

@@ -79,7 +79,7 @@ class ElectrumClient(
                 listenJob = listen(socket)
                 true
             } catch (ex: Throwable) {
-                logger.warning(ex) { "electrum connection handshake failed: " }
+                logger.warning { "electrum connection handshake failed: ${ex.message}" }
                 val ioException = when (ex) {
                     is TcpSocket.IOException -> ex
                     else -> TcpSocket.IOException.Unknown(ex.message, ex)
@@ -111,7 +111,7 @@ class ElectrumClient(
                 socket
             }
         } catch (ex: Throwable) {
-            logger.warning(ex) { "could not connect to electrum server: " }
+            logger.warning { "could not connect to electrum server: ${ex.message}" }
             val ioException = when (ex) {
                 is TcpSocket.IOException -> ex
                 else -> TcpSocket.IOException.ConnectionRefused(ex)
@@ -160,7 +160,7 @@ class ElectrumClient(
         // We use a SupervisorJob to ensure that our CoroutineExceptionHandler is used and exceptions don't propagate
         // to our parent scope: we simply disconnect and wait for the application to initiate a reconnection.
         val job = scope.launch(CoroutineName("electrum-client") + SupervisorJob() + CoroutineExceptionHandler { _, ex ->
-            logger.warning(ex) { "electrum connection error: " }
+            logger.warning { "electrum connection error: ${ex.message}" }
             socket.close()
             val ioException = when (ex) {
                 is TcpSocket.IOException -> ex