Fix the processing of apdus across multiple sources

[yrichard-ledger]

Description

This PR fixes edge cases when several apdus are sent to the device from different media.

The expected behaviour when two apdus are received in parallel is now:
* The first apdu processing is not impacted by the second one
* The second apdu is not processed and the device replies with an error SWO_IOL_STA_02 (0x1302)

This PR also adds a set of functions so that an application can restrict the apdu source to a single media.
This is intended to lock the media during a complex flow of apdus. In particular during an app installation
we can now reject automatically apdus from other medias

Changes include

• [*] Bugfix (non-breaking change that solves an issue)
• [*] New feature (non-breaking change that adds functionality)
• Breaking change (change that is not backwards-compatible and/or changes current functionality)
• Tests
• Documentation
• Other (for changes that might not fit in any category)

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 35.76%. Comparing base (cb5cfae) to head (af90253).
⚠️ Report is 1049 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #451   +/-   ##
=======================================
  Coverage   35.76%   35.76%           
=======================================
  Files          13       13           
  Lines        1591     1591           
=======================================
  Hits          569      569           
  Misses       1022     1022           

Flag	Coverage Δ
unittests	35.76% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[tdejoigny-ledger]

@yrichard-ledger did you manage the case where we receive a new APDU (via BLE) when still processing the previous APDU (no answer provided) received also via BLE ?

[yrichard-ledger]

@yrichard-ledger did you manage the case where we receive a new APDU (via BLE) when still processing the previous APDU (no answer provided) received also via BLE ?

Yes, whatever the media, if we receive a new APDU while the previous apdu is still processing the SDK will reply with SWO_IOL_STA_02 (0x1302)

[tdejoigny-ledger]

@yrichard-ledger as discussed, could we revisit this topic? I realize that we had already encountered some problematic cases with the BT here.
cc: @nroggeman-ledger