Fix for pump manager returns bogus podSuspended

[marionbarker]

Purpose

This PR fixes a problem reported by Trio users Trio Issue 468 in which the pump manager can sometimes report podSuspended following an uncertain comm event.

Background

An earlier PR #47 added one improvement for automatically recovering from uncertain comms but increased the incidence of the podSuspended being returned from the pump manager when the pod was not actually suspended.

Proposed Solution

This PR adds tryToValidateComms which, if successful, enables the pump manager to return the updated response from getStatus.

It also modifies some guard statements so that a podSuspended is only returned when the last message received from the pod indicates the pod is actually suspended.

The goal is to have the PumpManager return the true pod status, if possible.

[marionbarker]

Status

LGTM

Code inspection

The changes for OmniKit exactly parallel the OmniBLE PR 141 changes.

Testing

Most of the testing was done with the rPi and the DASH version of the PR.

Use a Trio-dev test phone (commit 92294ab8e), SE running iOS 18.3 and connect an Eros pod using an EmaLink.
Use Nightscout as a CGM.

These are the functions that contain a call to tryToValidateComms (the new function):

• (done) setTime
• (done) setBasalSchedule
• (done) setConfirmationBeeps
• (done) setSilencePod
• (done) suspendDelivery
• (done) resumeDelivery
• (done) enactBolus
• (done) runTemporaryBasalProgram

Do some kind of test with each function. Put (done) in front of each function when it was exercised at least once.

• move the EmaLink out of range and then bolus (got no RileyLink available)
• change time on phone, and update pump time, then restore
• suspend and then resume delivery - this takes care of setBasalSchedule, suspendDelivery and resumeDelivery
• change expiration notification time
• turn on Silence pod
• turn on a Manual Temp Basal