seata all 1.6 at模式 在transport.heartbeat=false时出现channel不断重复删除和注册的bug

//file.conf
```
transport {
# tcp udt unix-domain-socket
type = "TCP"
enableRmClientBatchSendRequest = true
enableTmClientBatchSendRequest = true
#NIO NATIVE
server = "NIO"
#enable heartbeat
heartbeat = false //设置为false会引起channel不断重复删除和注册
#thread factory for netty
threadFactory {
bossThreadPrefix = "NettyBoss"
workerThreadPrefix = "NettyServerNIOWorker"
serverExecutorThread-prefix = "NettyServerBizHandler"
shareBossWorker = false
clientSelectorThreadPrefix = "NettyClientSelector"
clientSelectorThreadSize = 1
clientWorkerThreadPrefix = "NettyClientWorkerThread"
# netty boss thread size,will not be used for UDT
bossThreadSize = 1
#auto default pin or 8
workerThreadSize = "default"
}
}
service {
#vgroup->rgroup
vgroupMapping.my_test_tx_group = "default"
#only support single node
#default.grouplist = "127.0.0.1:8091"
#degrade current not support
enableDegrade = false
#disable
disable = false
}

client {
rm {
asyncCommitBufferLimit = 10000
lock {
retryInterval = 10
retryTimes = 1
retryPolicyBranchRollbackOnConflict = true
}
reportRetryCount = 1
tableMetaCheckEnable = false
reportSuccessEnable = true
}
tm {
defaultGlobalTransactionTimeout = 180000
commitRetryCount = 1
rollbackRetryCount = 1
}

undo {
dataValidation = true
logSerialization = "jackson"
logTable = "undo_log"
}
log {
exceptionRate = 100
}
}
```

上面是我file.conf文件，在transport.heartbeat=false时channel会不断重复删除和注册。seata服务器控制台输出的日志如下：


上图表现为channel不断变成 inactive，然后被删除，并且 TM 不断注册，感觉应该是个bug。

Reproduce the issue with the supplied file.conf, focusing on transport.heartbeat=false, and compare the server console logs with heartbeat enabled. Trace the channel inactive, deletion, and TM registration sequence; done means channels remain registered without repeated deletion and registration when heartbeat is disabled.

Written by the indexing model from the issue text.