BluetoothAudioHAL: Fix the latency and the number of frames were inconsistent

The Bluetooth Audio HAL uses 3 APIs to share the audio latency to
audioserver, so they can do the audio / video synchronization. Those
API's results have to be consistent in the presented number of frames,
and should be reset only when the output was re-opened. Because the HAL
queried information from the Bluetooth which might be reset after the
Bluetooth session restarted, and caused a conflict between current and
previous results. The media frameworks needed more works to be A/V
synchronous again, and users would see the video was frozen.

This CL checks the stack data, and there must be no big delta between
the stack and HAL, or one of them was ever reset, and needs to use local
counters instead.

Bug: 137978401
Test: Switch active device and codec manually
Change-Id: I35bffa834c0de2e8b36e99a96b4a70738cc2b639