SAP: Fix missing connect response when call ongoing at connect

The CALL_ONGOING_STATE was set twice, causing the connect
response not to be sent to the peer device when there was an
ongoing call on DUT. This was violating the SAP Spec.

Bug: 24520367
Change-Id: I290d924870381a82a4abd8b6c42a6d0ebf55652f