*Description of the Issue:* This issue happens because the variable peripheralConnHandle isn't reset to LINKDB_CONNHANDLE_INVALID after requesting connection parameters update as the central.

The variable peripheralConnHandle is used to keep track on which peripheral a parameter update request is currently processed. It is also used to ensure there is one peripheral update request at a time (in 
GAP_UpdateLinkParamReq@gap_linkmgr) This variable is used for both central and peripheral. For the peripheral this variable is reset to
LINKDB_CONNHANDLE_INVALID in  gapPeriProcessConnUpdateCompleteEvt@gap_perilinkmgr.c but for the central the variable isn't reset. Which mean that GAP_UpdateLinkParamReq will crash with  bleAlreadyInRequestedMode when a peripheral role requests a connection update after doing it in the central role.