Set Tor logging to DEBUG level at startup

[ghost]

@chimp1984 requested a higher level of logging at startup due to issues we've been having with Tor.

As Tor currently defaults to logging at INFO level, this change turns on DEBUG logging during the startup phase.

Jul-08 11:43:04.383 [JavaFX Application Thread] INFO  b.c.a.BisqSetup: Init P2P network 
Jul-08 11:43:04.399 [NetworkNode-9999] INFO  b.n.p.n.NewTor: Starting tor 
Jul-08 11:43:04.401 [JavaFX Application Thread] INFO  b.c.a.BisqSetup: walletInitialized=false, p2pNetWorkReady=false 
Jul-08 11:43:06.848 [NetworkNode-9999] INFO  o.b.n.tor.Tor: Starting Tor 
Jul-08 11:43:06.882 [NFO] DEBUG o.b.n.tor.Tor: Jul 08 11:43:06.880 [notice] Tor 0.4.5.10 (git-fd74f7628eba2525) running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1l, Zlib 1.2.8, Liblzma N/A, Libzstd N/A and Glibc 2.23 as libc. 
Jul-08 11:43:06.882 [NFO] DEBUG o.b.n.tor.Tor: Jul 08 11:43:06.880 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning 
Jul-08 11:43:06.882 [NFO] DEBUG o.b.n.tor.Tor: Jul 08 11:43:06.881 [notice] Read configuration file "/home/xxxxxxx/.local/share/Bisq/btc_mainnet/tor/torrc". 
Jul-08 11:43:06.883 [NFO] DEBUG o.b.n.tor.Tor: Jul 08 11:43:06.883 [notice] Opening Control listener on 127.0.0.1:0 
Jul-08 11:43:06.883 [NFO] DEBUG o.b.n.tor.Tor: Jul 08 11:43:06.883 [notice] Control listener listening on port 43721. 
Jul-08 11:43:06.883 [NFO] DEBUG o.b.n.tor.Tor: Jul 08 11:43:06.883 [notice] Opened Control listener connection (ready) on 127.0.0.1:43721 
Jul-08 11:43:06.883 [NFO] DEBUG o.b.n.tor.Tor: Jul 08 11:43:06.883 [notice] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 
Jul-08 11:43:08.170 [TorControlParser] DEBUG o.b.n.tor.Tor: CircuitStatus: 1 LAUNCHED  
Jul-08 11:43:08.955 [TorControlParser] DEBUG o.b.n.tor.Tor: CircuitStatus: 1 EXTENDED $9738F8F5C386CDAF5707D0DCED428F2813CA285F 
Jul-08 11:43:08.956 [TorControlParser] DEBUG o.b.n.tor.Tor: CircuitStatus: 1 BUILT $9738F8F5C386CDAF5707D0DCED428F2813CA285F 
[...]

(followed by lots of Tor debug messages)

[...]
Jul-08 11:43:22.192 [TorControlParser] DEBUG o.b.n.tor.Tor: hiddenService: HS_DESC UPLOADED [MYTORONIONADDRESS] UNKNOWN $EF46C4D668872EA21E8A1967E9902D13B7E95263~Quetzalcoatl 
Jul-08 11:43:22.192 [TorControlParser] INFO  o.b.n.tor.Tor: Hidden Service [MYTORONIONADDRESS].onion has been announced to the Tor network. 
Jul-08 11:43:22.199 [Thread-12] INFO  b.n.p.n.TorNetworkNode: 
################################################################
Tor hidden service published after 4016 ms. Socket=HiddenServiceSocket[addr=[MYTORONIONADDRESS].onion,port=9999]
################################################################ 
Jul-08 11:43:22.728 [TorControlParser] INFO  o.b.n.tor.Tor: Hidden Service [MYTORONIONADDRESS].onion has been announced to the Tor network. 
Jul-08 11:43:22.854 [TorControlParser] INFO  o.b.n.tor.Tor: Hidden Service [MYTORONIONADDRESS].onion has been announced to the Tor network. 
Jul-08 11:43:22.907 [TorControlParser] INFO  o.b.n.tor.Tor: Hidden Service [MYTORONIONADDRESS].onion has been announced to the Tor network. 

(once hidden service is published, Tor logging reverts to INFO)

[ripcurlx]

utACK