[RTT] Handle HAL concurrencly limitations on RTT availability
The chip may not support RTT in all modes. The change handles this
correctly: whenever the HAL cannot support RTT (e.g. for multi-mode
chips + switching to AP mode only) the framework will be notified
and can dispatch RTT availability notification to app (both when
becoming non-available and then when becoming available again).
This notification on exact status also fixes the following:
- Initialization is precise: i.e. won't try to execute RTT commands
on an as yet uninitialized chip
- Can revert an early "hack" which re-tried creating a new RTT
controller if the previous one simply stopped working
Bug: 79565105
Bug: 111218083
Test: unit tests (new ones)
Test: ACTS RangeApSupporting11McTest:test_rtt_in_and_after_softap_mode
Change-Id: Ib9ef75bb679cdb0f49384260112c06684f52c693
7 files changed