Fix for perpetual Insert Cannula "Pod Already Paired" errors

[itsmojo]

This rare event happened with Trio but could potentially happen with Loop or iAPS as the code involved is virtually identical in all cases. The straightforward logic modification will prevent being forever stuck in the Insert Cannula screen with a Pod Already Paired error in the future. See nightscout/Trio#380 for additional info.

• Add optional mock error Preview handling code
• Minor updates to match OmniBLE versions

[marionbarker]

Status

Success. LGTM.

Code Review

Code review looks good. This will return success in the rare case that the Insert Cannula screen is displayed after podAlreadyPaired is set. This will prevent the infinite loop in the UI that was reported in Trio Issue 380.

Tests

Test with Preview

I tested this using the Preview in Trio. (For some reason, the Preview in Loop never opens for me.)

Use the Preview without this patch.

• Insert cannula works fine

Use the Preview as provided by this PR, the insert cannula behaves as expected.

• Insert cannula works fine

Use the Preview with the modification of setting both mockError and mockPodAlreadyPairedError to true
and get the expected message in the Xcode debug log:

### insertCannula treating podAlreadyPaired as success

Remove the modification in OmniKitUI/ViewModels/InsertCannulaViewModel.swift from this patch and repeat the Preview test with the true setting. The debug log reports

### insertCannula encountered error Pod already paired, retrying after 3.0 seconds

followed by this Preview screenshot. This matches the error seen by the user who reported this.

Test with Phone

I did not test with a real pod on a phone.
I relied on the similarity between OmniKit and OmniBLE and used the OmniBLE testing with an rPi DASH simulator.

[ps2]

LGTM!