Fix: CMSIS-DAP transfer failure handling

[dragonmux]

Detailed description

While helping Sid debug some really curious target behaviour from the Ambiq Apollo SoC's, he ran into an issue where ORBTrace would report the device gave a no-response response to a DAP_TRANSFER and BMDA would fail to pick up on that, pretending the DP register read worked just fine and gave a response of 0.

This PR corrects this behaviour by improving the perform_dap_transfer() error handling, allowing the detection of sequences such as

-> dap_transfer (1 requests)
 command: 05 00 01 06
response: 05 01 01 00 00 00 f4
dap_read_reg: 04 -> f4000000
dp_read 0004 f4000000
Read CTRL/STAT: 0xf4000000
-> dap_transfer (1 requests)
 command: 05 00 01 06
response: 05 01 07
dp_read 0004 00000000
Read CTRL/STAT: 0x00000000

With this change, the request will by noted as having triggered no-response and dap_dp_reg_read() will attempt to perform protocol recovery and re-try the read.

Your checklist for this pull request

• I've read the Code of Conduct
• I've read the guidelines for contributing to this repository
• It builds for hardware native (make PROBE_HOST=native)
• It builds as BMDA (make PROBE_HOST=hosted)
• I've tested it to the best of my ability
• My commit messages provide a useful short description of what the commits do

Closing issues

[esden]

LGTM :)