Update dev to 3.14.2

[marionbarker]

Purpose: Prepare for updating dev to version 3.14.2

With this PR, we are preparing for the next update to dev. The plan is this PR, when merged, will be followed shortly thereafter with a release to main using the same version number.

Method

Collect updates to dev branch prior to merge into dev.

• When ready and approved, this PR will be merged into dev as version 3.14.2

The Details section of this PR will be updated with each commit added to this PR. Before each commit is pushed, the build is tested locally with Xcode and Browser Build.

Details

• Bump version to 3.14.2
• update Loop: support OmnipodKit, see Loop PR 2426 Support use of OmnipodKit
• updated OmniBLE: fix identifier for 17e for Pod Keep Alive, see OmniBLE PR 170 fix: Apple model identifier for 17e is now correct
• update GitHub action to use Xcode 26.4
• update to fastlane 2.335.0
• add submodule OmnipodKit (see notes below)
• add submodule MedtrumKit
• add submodule EversenseKit

WARNING - before this PR is merged, the last action will be to remove OmniBLE and OmniKit from the workspace.

• once that change happens, Pod users with v3.14.2 will need to stick with v3.14.2 or newer
• ⚠️ after the commits where OmniBLE and OmniKit are removed, an active Pod will automatically transition to the new OmnipodKit, which is found in 3.14.2 and newer

OmnipodKit

What

Adds OmnipodKit as a new submodule.

• OmnipodKit is the unified Omnipod driver that handles both Eros and DASH pods through one pump manager, and replaces both OmniKit (Eros) and OmniBLE (DASH)
• Over the last six months, a number of UI/UX updates were inserted into OmnipodKit

Why

Pod-type fragmentation across two separate pump managers means duplicated DIY maintenance work (two trees of fixes, two compatibility matrices, two telemetry profiles). OmnipodKit consolidates the protocols into a single codebase.

As a Pod users - what do I need to do

Active-pod states from the old managers are automatically migrated to the new OmnipodKit manager

• Existing Pod users should notice some layout and wording difference
• New Pod users have to choose All Omnipod Types to use Pods and then after onboarding will see a screen asking the Pod Type: Classic (Eros) or DASH

[ps2]

LGTM!