Compare FS Ratio Live - engagment handling changes

[quadcom]

**moved from core issues

When this step is triggered, it will cancel the encoding process by throwing an error on the encode node. This immediately drops the job into the error bin. But there could be a better way of handling this situation. Yes, it should stop the encoding process but there should be a path for the job to go for alternate processing or alternate job management.

In my case, if the encoding is going to be larger than the existing file, I would still want the extra content to be removed (off lang SRT, extra audio tracks etc) and the resulting streams remuxed with my stream tags on the 0track stream to keep track of what has gone through the system. At present this is not an option and the job simply errors out and the file stays as is. If I were to use the error path from the encoder node, ANY error would be sent down the alternate path which is not appropriate as encodes could fail for any number of reasons.

Describe the solution you'd like
Add a secondary output path for the live ratio monitoring to direct jobs that have triggered the cancellation down a different path in the flow. Ensure the encoding process disregards cancel signals from this node so the job is not tracked as an error.

Describe alternatives you've considered
There are no alternative approaches to handle this situation that I could determine. Please correct me if I am wrong on this.