Streaming Session fires onCallEnded twice
<!--
Please DO NOT DELETE THIS TEMPLATE or your issue may be closed immediately.
Before opening an issue, search for open and closed GitHub issues that match your situation.

If this is a Live Stream issue please go back and use the Live Streaming issue template.
-->

# Bug Report

### Describe the Bug
The `onCallEnded` subject on `StreamingSession` is fired twice when a live stream is stopped manually

### To Reproduce
Steps to reproduce the behavior:
 - Create an api client, and call `streamVideo` on a camera
 - Subscribe to the `streamingSession.onCallEnded` subject (eg, to print a message to the log)
 - Invoke `streamingSession.stop()` on the object that is returned
 - Note that the handler is called twice, once immediately upon calling `stop()` and once more when the ffmpeg process exits

### Expected behavior
Pre-10.0 versions of the API only fired this event one time, once the ffmpeg process had actually completed. This would seem to be the most appropriate behavior

### Environment
<!-- ✍️edit: -->
 - OS: Alpine Linux
 - Node.js: 16.14.2
 - ring-client-api: 11.0
