Bluetooth MESH qualification tests regressions due to Tinycrypt deprecation

[sjanc]

Describe the bug
Bluetooth MESH qualification tests regressions after #79931 merge

This is when executed on both nRF52 and nRF53.

To Reproduce
Execute DFUM/SR/FD/BV-01-C qualification test case with AutoPTS.

Expected behavior
Tests pass

Impact
Bluetooth Mesh qualification is affected

Logs and console output
....
[00:00:13.643,676] bt_mesh_main: Primary Element: 0x0002
[00:00:13.643,707] bt_mesh_main: Failed to import device key
[00:00:13.643,707] bt_mesh_provisionee: Failed to provision (err -5)
....
[00:00:42.123,748] bttester: tester_event: service 0x04 opcode 0x8f
[00:00:42.130,859] bt_mesh_net_keys: Unable to generate beacon key
.....

This is affecting multiple tests (mainly DFU and MBTM):

MESH/NODE/KR/BV-01-C - Key Refresh Procedure as Node via Configuration Client Messages
MESH/NODE/KR/BV-02-C - Key Refresh Procedure as Node via Secure Network Beacons
MESH/NODE/KR/BV-04-C - Key Refresh Procedure as Node via Mesh Private Beacons
MESH/NODE/KR/BV-03-C - Key Refresh Procedure Skipping Phase 2 via Secure Network Beacons
MESH/NODE/KR/BV-05-C - Key Refresh Procedure Skipping Phase 2 via Mesh Private Beacons
MESH/CFGCL/KR/BV-01-C - Key Refresh as Configuration Client via Configuration Messages
MESH/CFGCL/KR/BV-02-C - Key Refresh as Configuration Client via Secure Network Beacons
MESH/CFGCL/KR/BV-05-C - Key Refresh with Reject listing via Mesh Private Beacons
MESH/CFGCL/KR/BV-03-C - Key Refresh with Reject Listing via Configuration Messages
MESH/CFGCL/KR/BV-04-C - Key Refresh with Reject Listing via Secure Network Beacons
MESH/CFGCL/KR/BV-06-C - Key Refresh with Reject listing via Mesh Private Beacons
MESH/NODE/KR/BI-01-C - Receive Config Key Refresh Phase Set Messages with Valid and Invalid Transition Values
MESH/NODE/KR/BI-02-C - Ignore New Keys During Key Refresh Procedure
MESH/NODE/KR/BI-04-C - Receive Messages with Old Keys During Configuration Client Key Refresh
MESH/NODE/KR/BI-05-C - Receive Messages with Old Keys During Secure Network Beacon Key Refresh
MESH/NODE/KR/BI-06-C - Receive Messages with Old Keys During Mesh Private Beacon Key Refresh
MESH/NODE/FRND/FN/BV-14-C - Friend Key Refresh via Secure Network Beacons - Friend Node
MESH/NODE/FRND/FN/BV-25-C - Friend Key Refresh via Mesh Private Beacons - Friend Node
MESH/NODE/FRND/FN/BV-15-C - Friend Key Refresh via Configuration Client Messages - Friend Node
MESH/NODE/FRND/FN/BV-20-C - Adding another Friend Update upon reception of Secure Network Beacons - Friend Node
MESH/NODE/FRND/FN/BV-26-C - Adding another Friend Update upon reception of Mesh Private Beacons - Friend Node
MESH/SR/PROX/BV-23-C - Send Secure Network Beacon when Secondary NetKey Added
MESH/SR/PROX/BV-24-C - Send Mesh Private Beacon when Secondary NetKey Added
MESH/NODE/CFG/GPXY/BV-02-C - Network ID Advertising on Multiple Subnets
MESH/NODE/CFG/MP/BV-02-C - Disabling Publishing - AppKey/Config NetKey Deleted. This test case requires configuring TSPX_iut_model_id_used.
MESH/NODE/CFG/NKL/BV-01-C - Respond to Config NetKey Add and Get Messages
MESH/NODE/CFG/NKL/BV-02-C - Respond to Config NetKey Update Message
MESH/NODE/CFG/NKL/BV-03-C - Respond to Config NetKey Delete Message
MESH/NODE/CFG/NKL/BI-01-C - Respond to Config NetKey Update Message (Invalid NetKeyIndex)
MESH/NODE/CFG/NKL/BI-03-C - Respond to Config NetKey Add Message (Insufficient Resources)
MESH/NODE/CFG/AKL/BV-02-C - Respond to Config AppKey Update Message
MESH/NODE/CFG/AKL/BI-02-C - Respond to Config AppKey Update Message (Invalid AppKey Index and NetKey Index)
MESH/NODE/CFG/AKL/BI-04-C - Respond to Config AppKey Add Message (NetKeyIndex and AppKeyIndex Already Stored)
MESH/NODE/CFG/NID/BV-02-C - Node Identity Advertising on Multiple Subnets
MESH/NODE/CFG/NID/BV-03-C - Node Identity Config NetKey Deleted
MESH/NODE/CFG/HBP/BV-06-C - Disabling publishing of Heartbeat messages - Config NetKey Deleted
MESH/SR/RPR/LNK/BV-19-C - Link Active State with Unprovisioned Device over PB-ADV - Handle Network Key Removal
MESH/SR/PRB/PGPXY/BV-02-C - Private Network Identity Advertising on Multiple Subnets
MESH/SR/PRB/PNID/BV-02-C - Private Node Identity Advertising on Multiple Subnets
MESH/SR/PRB/PNID/BV-03-C - Private Node Identity NetKey Deleted
MESH/NODE/SBR/NET/BV-01-C - Receive Network Layer Message, DST as Unicast Address, IUT as Subnet Bridge
MESH/NODE/SBR/NET/BV-02-C - Ignore Replayed Network Layer Message
MESH/SR/BCM/BDS/BV-01-C - Bridge Directive State Add Behavior
MESH/SR/BCM/BDS/BV-02-C - Bridge Directive State Remove Behavior
MESH/SR/BCM/BDS/BV-03-C - Bridge Directive State Get Behavior
MESH/SR/BCM/BDS/BV-04-C - Bridge Directive State Subnets Get Behavior
MESH/SR/BCM/BDS/BV-05-C - Bridge Directive State Behavior - Error Condition
MESH/SR/BCM/BDS/BV-06-C - Bridge Directive State - Binding with NetKey List State
DFUM/SR/FD/BV-48-C - Firmware Distribution Apply - Transfer Success Distribution Phase
DFUM/SR/FD/BV-59-C - Firmware Distribution Update - IUT Updates Itself
DFUM/SR/FD/BV-01-C - Receive Firmware Distribution Capabilities Get
DFUM/SR/FD/BV-02-C - Receive Firmware Distribution Node List messages
DFUM/SR/FD/BV-03-C - Receive Firmware Distribution Nodes Delete All-Failed Distribution Phase
DFUM/SR/FD/BV-04-C - Receive Firmware Distribution Nodes Delete All-Completed Distribution Phase
DFUM/SR/FD/BV-05-C - Upload Firmware - BLOB Transfer
DFUM/SR/FD/BV-06-C - Upload Firmware - OOB
DFUM/SR/FD/BV-07-C - Firmware Distribution Upload Start - Transfer Error
DFUM/SR/FD/BV-08-C - Firmware Distribution Upload Start - Transfer Success
DFUM/SR/FD/BV-09-C - Firmware Distribution Upload Start - Unsupported Size
DFUM/SR/FD/BV-10-C - Firmware Distribution Upload Start - Ongoing Transfer
DFUM/SR/FD/BV-11-C - Firmware Distribution Upload Start - New OOB Request
DFUM/SR/FD/BV-12-C - Firmware Distribution Upload Start - No Upload Space
DFUM/SR/FD/BV-13-C - Firmware Distribution Upload OOB Start - Transfer Error
DFUM/SR/FD/BV-14-C - Firmware Distribution Upload OOB Start - Transfer Success
DFUM/SR/FD/BV-15-C - Firmware Distribution Upload OOB Start - Unsupported URI
DFUM/SR/FD/BV-16-C - Firmware Distribution Upload OOB Start - Malformed URI
DFUM/SR/FD/BV-17-C - Firmware Distribution Upload OOB Start - Ongoing Transfer
DFUM/SR/FD/BV-18-C - Firmware Distribution Upload OOB Start - New BLOB Upload Request
DFUM/SR/FD/BV-19-C - Firmware Distribution Upload Cancel - Transfer Error
DFUM/SR/FD/BV-20-C - Firmware Distribution Upload Cancel - Transfer Success
DFUM/SR/FD/BV-21-C - Firmware Distribution Upload Cancel - Transfer Active
DFUM/SR/FD/BV-22-C - Firmware Distribution Upload Cancel - OOB Transfer Active
DFUM/SR/FD/BV-23-C - Receive Firmware Distribution Firmware List messages
DFUM/SR/FD/BV-24-C - Receive Firmware Distribution Firmware List Delete messages
DFUM/SR/FD/BV-25-C - Firmware Distribution Procedure
DFUM/SR/FD/BV-26-C - Reject Firmware Distribution Start
DFUM/SR/FD/BV-27-C - Firmware Distribution Start - Completed Distribution Phase, Different Request
DFUM/SR/FD/BV-28-C - Firmware Distribution Start - Completed Distribution Phase, Same Request
DFUM/SR/FD/BV-29-C - Firmware Distribution Start - Distribution Phase Failed
DFUM/SR/FD/BV-30-C - Firmware Distribution Start - Transfer Active Distribution Phase, Same Request
DFUM/SR/FD/BV-31-C - Firmware Distribution Start - Transfer Active Distribution Phase, Different Request
DFUM/SR/FD/BV-32-C - Firmware Distribution Start - Transfer Success Distribution Phase, Same Request
DFUM/SR/FD/BV-33-C - Firmware Distribution Start - Transfer Success Distribution Phase, Different Request
DFUM/SR/FD/BV-34-C - Firmware Distribution Start - Cancel Active Distribution Phase, Different Request
DFUM/SR/FD/BV-35-C - Firmware Distribution Start - Transfer Suspended Phase, Same Request
DFUM/SR/FD/BV-36-C - Firmware Distribution Start - Transfer Suspended Phase, Different Request
DFUM/SR/FD/BV-37-C - Firmware Distribution Cancel - Completed Distribution Phase
DFUM/SR/FD/BV-38-C - Firmware Distribution Cancel - Failed Distribution Phase
DFUM/SR/FD/BV-39-C - Firmware Distribution Cancel - Transfer Active Distribution Phase
DFUM/SR/FD/BV-40-C - Firmware Distribution Cancel - Transfer Success Distribution Phase
DFUM/SR/FD/BV-41-C - Firmware Distribution Cancel - Idle Distribution Phase
DFUM/SR/FD/BV-42-C - Firmware Distribution Cancel - Cancel Active Distribution Phase
DFUM/SR/FD/BV-43-C - Firmware Distribution Cancel - Apply Active Distribution Phase
DFUM/SR/FD/BV-44-C - Firmware Distribution Cancel - Transfer Suspended Distribution Phase
DFUM/SR/FD/BV-45-C - Firmware Distribution Apply - Completed Distribution Phase
DFUM/SR/FD/BV-46-C - Firmware Distribution Apply - Failed Distribution Phase
DFUM/SR/FD/BV-47-C - Firmware Distribution Apply - Transfer Active Distribution Phase
DFUM/SR/FD/BV-49-C - Firmware Distribution Apply - Idle Distribution Phase
DFUM/SR/FD/BV-50-C - Firmware Distribution Apply - Verifying Update Phase
DFUM/SR/FD/BV-51-C - Firmware Distribution Apply - Transfer Suspended Distribution Phase
DFUM/SR/FD/BV-52-C - Firmware Distribution Suspend - Idle Distribution Phase
DFUM/SR/FD/BV-53-C - Firmware Distribution Suspend - Transfer Active Distribution Phase
DFUM/SR/FD/BV-54-C - Firmware Distribution Suspend - Transfer Success Distribution Phase
DFUM/SR/FD/BV-55-C - Firmware Distribution Suspend - Completed Distribution Phase
DFUM/SR/FD/BV-56-C - Firmware Distribution Suspend - Failed Distribution Phase
DFUM/SR/FD/BV-57-C - Firmware Distribution Suspend - Transfer Success Distribution Phase
MBTM/SR/BT/BV-01-C - Transfer Block Sequence, Push BLOB Transfer Mode
MBTM/SR/BT/BV-02-C - Transfer Block Sequence, Pull BLOB Transfer Mode
MBTM/SR/BT/BV-03-C - BLOB Capabilities
MBTM/SR/BT/BV-04-C - BLOB Transfer Procedure, Push BLOB Transfer Mode
MBTM/SR/BT/BV-06-C - BLOB Transfer Timeout
MBTM/SR/BT/BV-07-C - Pull BLOB Transfer - Chunk Timeout
MBTM/SR/BT/BV-08-C - Pull BLOB Transfer - Reception Timeout
MBTM/SR/BT/BV-09-C - BLOB Transfer Cancel - IUT in Waiting for Next Block Phase
MBTM/SR/BT/BV-11-C - BLOB Transfer Cancel - IUT in Idle Phase
MBTM/SR/BT/BV-12-C - BLOB Transfer Cancel - IUT in Waiting for Next Chunk Phase
MBTM/SR/BT/BV-13-C - BLOB Transfer Cancel - IUT in Complete Phase, Push Transfer Mode
MBTM/SR/BT/BV-14-C - BLOB Transfer Cancel - IUT in Complete Phase, Pull Transfer Mode
MBTM/SR/BT/BV-15-C - BLOB Transfer Cancel - IUT in Inactive Phase
MBTM/SR/BT/BV-16-C - BLOB Transfer Cancel - IUT in Suspended Phase
MBTM/SR/BT/BV-17-C - BLOB Transfer Start - IUT in Waiting for Next Block Phase
MBTM/SR/BT/BV-18-C - BLOB Transfer Start - IUT in Waiting for Next Chunk Phase
MBTM/SR/BT/BV-19-C - BLOB Transfer Start - IUT in Complete Phase, Push Transfer Mode
MBTM/SR/BT/BV-20-C - BLOB Transfer Start - IUT in Complete Phase, Pull Transfer Mode
MBTM/SR/BT/BV-21-C - BLOB Transfer Start - IUT in Suspended Phase
MBTM/SR/BT/BV-22-C - BLOB Transfer Start - IUT in Inactive Phase
MBTM/SR/BT/BV-23-C - BLOB Block Start - IUT in Idle Phase
MBTM/SR/BT/BV-24-C - BLOB Block Start - IUT in Waiting for Next Chunk Phase
MBTM/SR/BT/BV-25-C - BLOB Block Start - IUT in Complete Phase, Push Transfer Mode
MBTM/SR/BT/BV-26-C - BLOB Block Start - IUT in Complete Phase, Pull Transfer Mode
MBTM/SR/BT/BV-27-C - BLOB Block Start - IUT in Suspended Phase, Block Number Set
MBTM/SR/BT/BV-28-C - BLOB Block Start - IUT in Suspended Phase, Block Number Unset
MBTM/SR/BT/BV-29-C - BLOB Block Start - IUT in Inactive Phase
MBTM/SR/BT/BV-30-C - BLOB Transfer Start - Incompatible Parameters
MBTM/SR/BT/BV-31-C - BLOB Transfer Start - Invalid Parameters
MBTM/SR/BT/BV-32-C - BLOB Transfer Cancel - Invalid Parameters
MBTM/SR/BT/BV-33-C - BLOB Block Start - Invalid Parameters
MBTM/SR/BT/BV-34-C - BLOB Chunk Transfer - Invalid Parameters
MBTM/SR/BT/BV-35-C - BLOB Transfer Server State - Default Values
MBTM/SR/BT/BV-36-C - BLOB Block Get - IUT in Idle Phase
MBTM/SR/BT/BV-37-C - BLOB Block Get - IUT in Suspended Phase
MBTM/SR/BT/BV-38-C - BLOB Block Get - IUT in Inactive Phase
MBTM/SR/BT/BI-01-C - BLOB Transfer Start - RFU Bits
MBTM/SR/BT/BI-02-C - BLOB Transfer Start - Prohibited Transfer Mode
DFUM/SR/FU/BV-01-C - Receive Firmware Update Information, IUT as Target Node
DFUM/SR/FU/BV-02-C - Receive Firmware Update Validation Data Check, IUT as Target Node
DFUM/SR/FU/BV-03-C - Firmware Update - Verification Succeeded, IUT as Target Node
DFUM/SR/FU/BV-04-C - Firmware Update - Transfer Error, IUT as Target Node
DFUM/SR/FU/BV-05-C - Firmware Update - Verification Failed, IUT as Target Node
DFUM/SR/FU/BV-06-C - Firmware Update - Cancel BLOB, IUT as Target Node
DFUM/SR/FU/BV-07-C - Receive Firmware Update Start - Transfer Active Update Phase, IUT as Target Node
DFUM/SR/FU/BV-08-C - Receive Firmware Update Start - BLOB Trasfer Busy, IUT as Target Node
DFUM/SR/FU/BV-09-C - Firmware Update Apply, IUT as Target Node
DFUM/SR/FU/BV-10-C - Receive Firmware Update Cancel - Idle Phase, IUT as Target Node
DFUM/SR/FU/BV-11-C - Receive Firmware Update Cancel - Transfer Active Phase, IUT as Target Node
DFUM/SR/FU/BV-12-C - Receive Firmware Update Cancel - Transfer Error Phase, IUT as Target Node
DFUM/SR/FU/BV-13-C - Receive Firmware Update Cancel - Verification Succeeded Update Phase, IUT as Target Node
DFUM/SR/FU/BV-14-C - Receive Firmware Update Cancel - Verification Failed Update Phase, IUT as Target Node
DFUM/SR/FU/BV-15-C - Receive Firmware Update Cancel - Applying Update Phase, IUT as Target Node
DFUM/SR/FU/BV-16-C - Receive Firmware Update Start - Transfer Error Phase, IUT as Target Node
DFUM/SR/FU/BV-17-C - Receive Firmware Update Start - Verification Success Phase, IUT as Target Node
DFUM/SR/FU/BV-18-C - Receive Firmware Update Start - Verification Failed Phase, IUT as Target Node
DFUM/SR/FU/BV-19-C - Receive Firmware Update Start - Applying Update, IUT as Target Node
DFUM/SR/FU/BV-20-C - Receive Firmware Update Apply - Idle Phase, IUT as Target Node
DFUM/SR/FU/BV-21-C - Receive Firmware Update Apply - Transfer Error Phase, IUT as Target Node
DFUM/SR/FU/BV-22-C - Receive Firmware Update Apply - Transfer Active Phase, IUT as Target Node
DFUM/SR/FU/BV-23-C - Receive Firmware Update Apply - Verification Failed Phase, IUT as Target Node
DFUM/SR/FU/BV-24-C - Resume Firmware Transfer, IUT as Target Node
MBTM/CL/BT/BV-01-C - Transfer BLOB Procedure, Push BLOB Transfer Mode
MBTM/CL/BT/BV-02-C - Transfer BLOB Procedure, Pull BLOB Transfer Mode
MBTM/CL/BT/BV-03-C - Cancel Transfer Procedure
MBTM/CL/BT/BV-04-C - Transfer BLOB Procedure - Failure
MBTM/CL/BT/BV-05-C - Transfer BLOB Procedure - Transfer Timeout
MBTM/CL/BT/BV-06-C - Transfer BLOB Procedure - Partial Block Report Timeout
MBTM/CL/BT/BV-07-C - Transfer BLOB Procedure - Disable Receiver
MBTM/CL/BT/BV-08-C - Get Transfer Progress Procedure

[valeriosetti]

Based on an offline discussion with @alxelax he thinks that #82319 can help in fixing these problems. Therefore I propose for that PR to be merged and then re-run these tests.

[sjanc]

OK, I'll trigger PR run on that with some smoke testing