ActiveModeWarden: Exit emergency mode should not start a new ClientModeManager if one is already present

Currently, upon exiting emergency mode, ActiveModeWarden starts
a new ClientModeManager, even if a ClientModeManager is already
present.

Instead, it should only start a new ClientModeManager if one
doesn't exist, and do nothing otherwise.

Bug: 174438512
Test: atest FrameworksWifiTests
Test: trigger test broadcast and manually verify Wifi is in correct state
      after exiting emergency mode
Change-Id: I91832784f432d71becc90950047bb3591cd75542
Merged-In: I91832784f432d71becc90950047bb3591cd75542
2 files changed
tree: 71fd6282c8c042c332bb3c242e8b56a3d53a61b7
  1. apex/
  2. service/
  3. metrics_pdd_hook.py
  4. PREUPLOAD.cfg