l2cap: Fix handling Enhanced Credit Connection response

This is a regression after
l2cap: Fix for REF responds with same DCIDs for different connections from IUT

The mentioned patch should check rcids which are different than 0.
Otherwise we might end up sending L2CAP Disconnection Request on 0:

> ACL Data RX: Handle 64 flags 0x02 dlen 26
      LE L2CAP: Enhanced Credit Connection Response (0x18) ident 2 len 18
        MTU: 64
        MPS: 247
        Credits: 2
        Result: Some connections refused – not enough resources available (0x0004)
        Destination CID: 66, Source CID: 68
        Destination CID: 0
        Destination CID: 0
        Destination CID: 0
        Destination CID: 0
> HCI Event: Number of Completed Packets (0x13) plen 5
        Num handles: 1
        Handle: 64
        Count: 2

< ACL Data TX: Handle 64 flags 0x00 dlen 12
      LE L2CAP: Disconnection Request (0x06) ident 3 len 4
        Destination CID: 0
        Source CID: 69
< ACL Data TX: Handle 64 flags 0x00 dlen 12
      LE L2CAP: Disconnection Request (0x06) ident 4 len 4
        Destination CID: 0
        Source CID: 70
< ACL Data TX: Handle 64 flags 0x00 dlen 12
      LE L2CAP: Disconnection Request (0x06) ident 5 len 4
        Destination CID: 0
        Source CID: 71
< ACL Data TX: Handle 64 flags 0x00 dlen 12
      LE L2CAP: Disconnection Request (0x06) ident 6 len 4
        Destination CID: 0
        Source CID: 72

Bug: 234817072
Test: Connect with remote supporting 1 EATT only
Merged-In: I9ad7993729d74918b8b2751a036d44a5ddd7fee7
Change-Id: I9ad7993729d74918b8b2751a036d44a5ddd7fee7
(cherry picked from commit 0f335669)