The config default inactivity timeout has long been used as a "cover up" to fix
an inexplicable connection leak that'd escape all the more intuitive different
timer transaction and connection level configs ATS supports
(https://docs.trafficserver.apache.org/en/latest/admin-guide/files/records.co
9.x (re)introduces a feature (it was accidentally "lost" during some unrelated
refactoring) that will allow to configure limits on max "active" connections
that can be allowed at any given time
(https://github.com/apache/trafficserver/pull/6754)
Given that this feature is based on tracking "acti