pHostapdState->vosEvent is a shared event for StartBss, StopBss and
Sta_Disassoc completion. When hdd calls WLANSAP_StopBss it waits on
this event assuming, StopBss completion will trigger the event. But:
1) DISASSOC event from one of the earlier STA comes late and falsely
   trigger the event (even before WLANSAP_StopBss complete).
2) This causes SAP restart sequence to be messed up and
3) followed by inconsistent vdev_id between host and firmware.
4) Because of this FW is then dropping MGMT packets sent from host and
5) hence clients are not able to connect to SAP.

Change-Id: Ib1f670ee0ab9dff7fab25f4402bbd278f014bea2
CRs-Fixed: 767351