1.Use iw tool to let dut connect to remote ap, dut is working on wlan0.
2.At same time, use hostapd to start sap also on interface wlan0.

In item1, before connect to ap, dut will do an internal scan to search ap,
if scan result matched configured ap profile, dut trys to connect to ap.

In item2, when starting sap, found it's sta mode it will try to disconnect
dut with remote ap and close sta session.

  #1 If ap start action happened in item1's scan period, trying disconnecting
  won't take effect as currently sta has not yet connected with remote ap.
  So after item1's scan finished, dut continues to do connection.

  #2 During closing sta session, sme issued eSmeCommandDelStaSession, as
  currently sta is doing connection, so session is in started status, this
  cause closure failed, so there is no chance to remove cmd in smeCmdActiveList.
  While cmd pending in smeCmdActiveList for 120s, driver issued crash.

The solution is in item1 after scan complete to check whether it's
needed to start following connection. If stop action has been issued
during scan period, then don't do the connection.

Change-Id: If632e21cb13277fba371ff1bf8df97febf856d09
CRs-Fixed: 923375