sm: use state var to track DHKEY_CHECK_COMMAND received

sm: use AES CMAC Engine to calculate g2 for numeric comparison

sm: extract g2_calculate

sm: use AES CMAC Engine to calculate f5 for dhkey check verification

sm: use AES CMAC Engine to calculate f6 for dhkey check verification

sm: use AES CMAC Engine to calculate f6 for dhkey check send

sm: prepare dhkey check to use AES CMAC Engine

sm: extract sm_sc_calculate_dhkey

sm: use AES Engine for f4 (confirm validation)

sm: use AES Engine for f4

sm: extract sm_sc_calculate_local_confirm

sm: add sm_cmac_general_start for aes_cmac calculation in secure connection functions

sm: use SM_SC_ for SC states

sm: verify confirm value with passkey entry in responder role

sm: send 'numeric comparison failed' on decline by app

sm: validate peer DHKey Check value

sm: validate Cb during passkey modes

sm: validate Cb during just works/numeric comparison

sm: don't calc random numbers for legacy pairing key distribution when using secure connections

sm: passkey entry for secure connections in initiator role

sm: numeric comparison for secure connections in initiator role

sm: just works for secure connections in initiator role

sm: keep track of security request before sm received connection complete

sm: verify peer Q lies on elliptic curve

sm: add sm_numeric_comparison_confirm(..) and use in le_counter