qcacld-3.0: Handle sap restart after opportunistic timer start failure

Currently, If hadware is not dbs capable opportunistic timer
can not be started. In function if_mgr_connect_complete
policy_mgr_check_n_start_opportunistic_timer fails to start
opportunistic timer in case of non-dbs hw and sap restart
doesn't happen.

Fix is not to validate status returned by
policy_mgr_check_n_start_opportunistic_timer to restart sap
in case of non-dbs hardware.

Change-Id: I3308a5c10341950d51419907cc767c09f967b7b1
CRs-Fixed: 2792764

components/cmn_services/interface_mgr/src/wlan_if_mgr_sta.c

@@ -120,11 +120,7 @@ QDF_STATUS if_mgr_connect_complete(struct wlan_objmgr_vdev *vdev,
 		if_mgr_enable_roaming(vdev, pdev, RSO_CONNECT_START);
 	}
 
-	status = policy_mgr_check_n_start_opportunistic_timer(psoc);
-	if (status) {
-		ifmgr_err("Failed to start dbs opportunistic timer");
-		return status;
-	}
+	policy_mgr_check_n_start_opportunistic_timer(psoc);
 
 	policy_mgr_check_concurrent_intf_and_restart_sap(psoc);