Investigate and Fix Invalid frame_id Error and Fix

[planetchili]

After hooking up logging to the Streamer component, we have noticed sporadic errors in the log about invalid_id. This error becomes prolific when replaying ETL files through the service. Culprit is likely the the Streamer itself or the middleware. Multiprocess debugging while pausing all processes should be sufficient to run this issue down.

[planetchili]

• ETL option in header causes divergent behavior
• ETL options also existing in service (Streamer) and client (StreamClient), but they are not being used consistently with header option
• Realtime has improper behavior that desyncs the current frame number from the next idx (this gives an "extra" buffer frame to allow the peek behavior to not trigger out of bounds error)
• Still can be triggered in real time if there are dropped frames at end
• Bad off-by-one bounds check means one invalid frame is read before error is triggered
• Invalid frame is zeroed before wrap around and treated as not presented, but after wrap it will potentially be used
• Race condition on use of header after destruction can cause a crash (probably rare)

[planetchili]

Current plan is to remove existing unused ETL paths, add flags to header for both playback and additionally backpressure, and re-introduce backpressure mechanism.
Bounds check should be fixed, initial frame number desync should be fixed, out of bounds read error should be removed (or downgraded).
Option flag should be added to allow frame number to initialize on the oldest available (rather than discarding all previously queued).