gap: assert pairing complete event for OOB if user does not provide OOB data

gap: emit gap pairing complete after calling gap_pin_code_negative

also asserts event for SSP pairing decline

gap: reject pin code request if security level 4 required

hci: fix crash on sending GAP_EVENT_PAIRING_STARTED and GAP_EVENT_PAIRING_COMPLETE

GAP: correct field order in GAP_EVENT_PAIRING_STARTED and GAP_EVENT_PAIRING_COMPLETE

gap: detect SC->Legacy downgrade on encryption change

fix build

gap: treat newly paired connection and aes-ccm encrypted connections as authenticated

hci.c: fix len field of GAP_EVENT_INQUIRY_RESULT

gap: reset requested_security_level on pairing complete

gap: reset requested_security_level on pairing complete

gap: send hci authentication required after remote features are available

hci: avoid assert sending sco via timers

gap: emit GAP_EVENT_PAIRING_STARTED and GAP_EVENT_PAIRING_COMPLETE for OOB Pairing

CVE-2020-26555: ignore NULL link key

CVE-2020-26555: reject connections to and from devices with same BD ADDR (fix)

CVE-2020-26555: reject connections to and from devices with same BD ADDR

hci: fix c++ build

hci: fix c++ build

gap: check if minimal service security level can be reached in responder role

l2cap: track minimal security level

l2cap: streamline secure connections only mode

If SC Only Mode is enabled, map all security levels to level 4 unless it is level 0

gap: secure connections only mode requires level 4 for all non-secure services

gap: send user confirmation negative reply if required security level cannot be met

gap: send IO Capabilities Negative Reply if Level 4 required but remote does not support SC