commit cdd2b36062fca9b5edc72e1e418c04b3cc2e3404
author markchien <markchien@google.com> Fri Feb 14 17:40:50 2020 +0800
committer markchien <markchien@google.com> Fri Feb 14 18:22:43 2020 +0800
tree 27d21887d8c245110634d21a5baf5c5069cf9f86
parent 26d8f5808bd920c7721d44507c485a6bc8286f3c

Fix testStartTetheringWithStateChangeBroadcast flaky

Before this change the test assume one active state event is followed by
zero or one availabe event:
AVAIALBE(wlan1) -> ACTIAVE(wlan1) -> AVAILALE(wlan1)

But actually Multiple tetherable wifi interfaces may be avaialbe during
the test:
AVAILABLE(wlan1) -> AVALIABLE(wlanX) -> .... -> ACTIVE(wlan1) ->
AVAIALBE(wlan1)

Additional, replacing ConnectivityManager usage to TetheringManager.

Bug: 148095484
Test: atest CtsTetheringTest
Change-Id: Id5db970c02f63f61802a18b599bf6905db619b42