net: wirelss: bcmdhd fixed disconnect issue for connecting status

Sometimes Framework issues connect and disconnect rapidly and continuously
with different APs.  In this case, the timing gap between connect and
disconnect is less than 20ms.  For this scenario, FW doesn't do anything
when DHD executes dissasoc while state of FW is associating status.  In
order to cancel current assoc procedure correctly, we need to call
scan_abort function, not DISASSOC.  FW will clean up ongoing assoc
procedure if FW is associating status.

b/18470879 Device stop responding after conducting rapid fire testing
           for making connection

Change-Id: Ib440da06eb10313c478c004d1d73ed1b4e29a201
Signed-off-by: Ecco park <eccopark@broadcom.com>
Signed-off-by: Iliyan Malchev <malchev@google.com>

Conflicts:
	drivers/net/wireless/bcmdhd/wl_cfg80211.c
Signed-off-by: flar2 <asegaert@gmail.com>