[fix][client] Fix idle connection release ignoring V5 watch sessions

[Dream95]

Motivation

When connectionMaxIdleSeconds is enabled, ConnectionPool periodically calls ClientCnxIdleState#doIdleDetect, which uses ClientCnx#idleCheck() to decide whether a pooled connection is idle. idleCheck() did not account for V5 registrations (dagWatchSessions, scalableConsumerSessions, scalableTopicsWatchers), while channelInactive treats them as live sessions on the connection. As a result, connections that still served scalable-topic watches or DAG watches could be marked idle and released, causing unnecessary disconnects and other errors.

Modifications

Added checks in ClientCnx#idleCheck() for dagWatchSessions, scalableConsumerSessions, and scalableTopicsWatchers

Verifying this change

• Make sure that the change passes the CI checks.

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

• Dependencies (add or upgrade a dependency)
• The public API
• The schema
• The default values of configurations
• The threading model
• The binary protocol
• The REST endpoints
• The admin CLI options
• The metrics
• Anything that affects deployment

Matching PR in forked repository

PR in forked repository: Dream95#7

[lhotari]

LGTM, thank you @Dream95

[Dream95]

/pulsarbot rerun-failure-checks