BLE Commisioning broken for TI examples

[andersbangGF]

Problem

We have tested BLE commissioning with chip-tool on the TI platform and it seems to have broken due to #13330 .
The DUT log is attached - Seems to never succeed in sending the response to the tool and just hangs. Tested with ToT pump-app and lock-app and ToT ChipTool (Android, Mac).

Dut log since this issue (just hangs after this):
Enabled BLE Advertisements local and remote recv window sizes = 6 selected BTP version 4 using BTP fragment sizes rx 244 / tx 244. BLE EndPoint 0x2000fb58 Connection Complete Received message of type 0xhx with protocolId (32, 0) and MessageCounter:0 on exchange 52737g Handling via exchange: 51815r, Delegate: 0x200123d8 Received PBKDF param request Peer assigned session ID 1 Found MRP parameters in the message Including MRP parameters in PBKDF param response Prepared unauthenticated message 0x2001a194 to 0x0000000000000000 (0) of type 0xhx and protocolId (33, 0) on exchange 0g with MessageCounter:114. Sending unauthenticated msg 0x2001a194 with MessageCounter:1611028191 to 0x0000000000000000 at monotonic time: ld msec

DUT log before (proceeds with the commissioning process):
Enabled BLE Advertisements local and remote recv window sizes = 6 selected BTP version 4 using BTP fragment sizes rx 244 / tx 244. BLE EndPoint 0x2000fbb8 Connection Complete Received message of type 0xhx with protocolId (32, 0) and MessageCounter:0 on exchange 38414� Handling via exchange: 64912r, Delegate: 0x20012430 Received PBKDF param request Peer assigned session ID 1 Found MRP parameters in the message Including MRP parameters in PBKDF param response Prepared plaintext message 0x2001a1d4 to 0x0000000000000000 (0) of type 0xhx and protocolId (33, 0) on exchange 0� with MessageCounter:114. Sending plaintext msg 0x2001a1d4 with MessageCounter:3357128026 to 0x0000000000000000 at monotonic time: ld msec Sent PBKDF param response