rabbit_channel_tracking: Don't update channel tracking directly when a connection is closed

Tracking is already taken care of when each channel is closed.

Removing this concurrent call to `unregister_tracked()` fixes a
double-decrease of the counter. The reason is the counter is updated
outside of a transaction and is therefore sensitive to concurrent
read/modify/write sequences.

A transaction would be a more appropriate solution, but it may be too
resources-intensive in the scenario of high connection/channel churn.

0 files changed, 0 insertions, 0 deletions