[pulsar-client-cpp] Excessive locking cause significant performance degradation

**Describe the bug**
Implementation of statistics in cpp client have two concurrency issues.

1. ProducerStatsImpl (and ConsumerStatsImpl) classes use a single shared lock to protect access to internal data. The lock is taken on each sent or received message. Under high load this shared lock causes signficant contention and performance degradation.
Profiler shows that sending and receiving threads block each-other.


Since sending and receving functions access different member subset they should be protected by different mutex or other approach should be selected.
As example after patching issue I've got about 1/3 throughtput improvement. As you can see on screenshot below threads are witing on I/O but not on mutexes.

2. ProducerStatsImpl implementation has races between destructor and DeadlineTimer callback. Consider following scenario:

1. ProducerStatsImpl destructor acquire the mutex
2. DeadlineTimer calls calback flushAndReset and blocked on mutex
3. ProducerStatsImpl calls timer.cancel and cancel any pending operation but it cannot cancel already executed callback at step 2
4. ProducerStatsImpl destructor release mutex
5. DeadlineTimer acquire the mutex
6. ProducerStatsImpl destructor destroy object
7. DeadlineTimer callback access to deallocated memory

Are you willing accept PR for issue number one or both?

Read the ProducerStatsImpl and ConsumerStatsImpl implementations and their DeadlineTimer callback path first. Use high-load profiling to verify lock contention; done means reducing send/receive mutex contention and preventing callbacks from accessing destroyed ProducerStatsImpl, for the accepted scope.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.