This will start building out our unit test suite for OmniBLE. I have about 50% of the Kotlin tests rewritten for Swift. To run the unit tests, you need to:

1. Open Loop Workspace
2. Build the Loop Workspace target for the iPhone simulator 1x to build the required simulator dependencies.
3. Run OmniBLE tests for iPhone Simulator from Xcode Workspace.

This includes a fairly large update to how connections are managed in OmniBLE.

• Multiple ready-to-pair pods are detected during pairing, so the user does not inadvertently pair to the wrong pod.
• BLE connection identifier is tracked to ensure reconnection to the correct peripheral
• During session restoration, iOS may have maintained connection to the pod, so that from the pod's point of view, nothing has changed, and creating a session is not needed; changes are included to handle this situation, and not attempt to recreate a session.

It also includes changes to work with the latest Loop dev code, and, in fact, will only compile with dev LoopKit. So I recommend this patch does not land into master until a suitable maintenance branch for FreeAPS is found.

If you create a dev branch, I can re-submit this PR to point there.

Calls to configureAndRun need to currently be done on the queue since that hits areas of code protected by queue assertions. This seems like a simple fix by just removing the call to configureAndRun, since the call to perform() already calls configureAndRun on the queue.

The improvements from sraka1 have been merged and tested in the marionbarker repo (rk-dev-01 branch). I suggest these be merged (or alternately, this could be pulled directly from sraka1).

I've been working at aligning the messaging that is sent from AndroidAPS vs OmniBLE. One difference is how the ID is incremented. I think we can revert this once we successfully figured out Pod Pariing. But in the meantime, this ensures we are sending the same payloads as AndroidAPS.

• MessageTransport/CRC16.swift -> OmnipodCommon/CRC16.swift
• MessageTransport/Message.swift -> OmnipodCommon/Message.swift
• MessageTransport/MessageBlocks/* -> OmnipodCommon/MessageBlocks/*
• MessageTransport/MessageTransport.swift -> PumpManager/MessageTransport.swift
• MessageTransport/StringLengthPrefixEncoding.swift -> Bluetooth/StringLengthPrefixEncoding.swift
• Model/AlertSlot.swift -> OmnipodCommon/AlertSlot.swift
• Model/BasalDeliveryTable.swift -> OmnipodCommon/BasalDeliveryTable.swift
• Model/BasalSchedule.swift -> OmnipodCommon/BasalSchedule.swift
• Model/BeepType.swift -> OmnipodCommon/BeepType.swift
• Model/FaultEventCode.swift -> OmnipodCommon/FaultEventCode.swift
• Model/Pod.swift -> OmnipodCommon/Pod.swift
• Model/PodProgressStatus.swift -> PumpManager/PodProgressStatus.swift
• Model/UnfinalizedDose.swift -> OmnipodCommon/UnfinalizedDose.swift
• PumpManager/PodCommsSession+LoopKit.swift -> OmnipodCommon/PodCommsSession+LoopKit.swift
• PumpManager/PodDoseProgressEstimator.swift -> OmnipodCommon/PodDoseProgressEstimator.swift
• PumpManager/PodInsulinMeasurements.swift -> OmnipodCommon/PodInsulinMeasurements.swift
• Delete now empty MessageTransport & Model directories
• Alphabetize directory contents

When an error occurs communicating with the pump, the thread seemed blocked from returning. This should repsect the timeouts that are passed by the client.

Incorporate the Bluetooth improvements found in ps2/OmniBLE dev-protocols branch, while maintaining the older Loop master and FreeAPS protocols.

The changes to files are post commit 6e2dddd.