Fix live metrics race condition

[trask]

No description provided.

[Copilot]

Pull Request Overview

This PR addresses a race condition in the live metrics telemetry collector by introducing a read–write lock around the core counter operations.

• Adds a ReadWriteLock to synchronize getAndRestart, peek, and per-item add logic.
• Refactors helper methods to accept a Counters instance rather than fetching it internally.
• Introduces early type and null checks to skip locking when no counters are available or for unsupported telemetry.

Comments suppressed due to low confidence (2)

sdk/monitor/azure-monitor-opentelemetry-autoconfigure/src/main/java/com/azure/monitor/opentelemetry/autoconfigure/implementation/quickpulse/QuickPulseDataCollector.java:62

• [nitpick] The field name lock is very generic; consider renaming it to something like countersLock or rwCountersLock to clarify its purpose.

    private final ReadWriteLock lock = new ReentrantReadWriteLock();

sdk/monitor/azure-monitor-opentelemetry-autoconfigure/src/main/java/com/azure/monitor/opentelemetry/autoconfigure/implementation/quickpulse/QuickPulseDataCollector.java:94

• This method still uses synchronized instead of the new ReadWriteLock, causing mixed locking strategies that could lead to deadlock. Consider switching it to lock.readLock().lock()/unlock() or removing the synchronized keyword entirely.

    synchronized QuickPulseStatus getQuickPulseStatus() {