Handle PassedEndTime reservation state

[jmacauley]

SuPA has correctly implemented the NSI CS 2.1 state machine. The lifecycle state machine transitions from Created to Passed EndTime when the endTimeEvent is received. "PassedEndTime" is a stable state so the state machine will stay there until a terminate request is received. SENSE has limited state modeling so cannot understand this intermediate state and gets confused when it sees a reservation still in place after endTime.

Requested fix is to filter out any reservations from the model in the PassedEndTime state.