Tm w3q bugfix -- temdermint init multi times

[ping-ke]

0 number=79075 hash=86c256..385fa9 dirty=0.00B INFO [05-31|01:37:13.397] Finalizing commit of block height=79076 hash=245cfe..3a9d40 INFO [05-31|01:37:13.400] Imported new chain segment blocks=1 txs=0 mgas=0.000 elapsed=2.670ms mgasps=0.000 number=79076 hash=245cfe..3a9d40 dirty=0.00B INFO [05-31|01:37:14.111] Finalizing commit of block height=79077 hash=91858c..034680 INFO [05-31|01:37:14.113] Imported new chain segment blocks=1 txs=0 mgas=0.000 elapsed=1.485ms mgasps=0.000 number=79077 hash=91858c..034680 dirty=0.00B INFO [05-31|01:37:14.407] Block synchronisation started INFO [05-31|01:37:14.407] Mining aborted due to sync INFO [05-31|01:37:14.415] Downloader queue stats receiptTasks=0 blockTasks=0 itemSize=223.53B throttle=8192 INFO [05-31|01:37:14.429] Imported new chain segment blocks=4 txs=0 mgas=0.000 elapsed=14.219ms mgasps=0.000 number=79081 hash=a75c21..d25c2b dirty=0.00B INFO [05-31|01:37:14.430] Create a temp node key CRIT [05-31|01:37:14.432] tm.Init err="failed to listen on any addresses: [listen udp4 0.0.0.0:33334: bind: address already in use listen udp6 [::]:33334: bind: address already in use]"

this issue will cause the node to fail if it needs to sync block before starting mining. the issue is caused by the tm.Init been cause for multi-time, which should not happen

[qizhou]

I feel we should separate the diff you made to the configuration and relayer to another PR.