Pulsar Proxy HashedWheelTimer and Frame Exception

[xuesongxs]

Describe the bug

[codelipenghui]

Thanks @xuesongxs . Seems the problem is the proxy creates a Pulsar client for each connection since the proxy need to do the authentication by the client. Since each Pulsar client will create a HashedWheelTimer, so the error occurs and more HashedWheelTimer will waste a lot of cpu cycles(the tick time is 1ms in the Pulsar client).

I think we should make the HashedWheelTimer static in the Pulsar client.

[lhotari]

It turns out the PulsarClientImpl isn't needed at all in Pulsar Proxy. There's a PR #13836 to optimize the resource usage of Pulsar Proxy. This reduces 2 threads per proxied connection which will help improve Pulsar Proxy scalability. Please review #13836