Livestreams: separate out video stream quality forcing between high-latency and low-latency clients
### Describe the feature request

For livestream viewing, separate out video stream quality forcing between high-latency and low-latency clients.

Assuming all stream qualities are available from Protect, this will have 3 major benefits:
1. For remote, if not transcoding, we will only transmux and save a lot of CPU.
2. For remote, if transcoding **and local is forced to High**, we will potentially transcode a smaller res stream thus saving CPU
3. For local, we can keep forcing to high and not transcoding without compromising remote performance.

The story behind this is my own setup:
- All video stream qualities available from Protect
- HKSV (hogging a lot of CPU)
- Livestream quality force to high <--- must-have for Local
- Livestream Local using to transmux <--- must-have
- Livestream Remote forced to transcode <---- inefficient compromise to due to requirements for Local

If remote livestreams had the freedom to choose the stream directly from the Protect controller, then no transcoding might be needed thus saving a lot of CPU. Even if transcoding would still be necessary for some cameras, this plugin could potentially pick a lower res stream thus saving CPU.

### Describe the proposed solution

1. In Video Feature Options, add the following 3 knobs:
- [ ] When viewing livestreams **from High-Latency clients**, force the use of the high quality video stream from the Protect controller.
- [ ] When viewing livestreams **from High-Latency clients**, force the use of the medium quality video stream from the Protect controller.
- [ ] When viewing livestreams **from High-Latency clients**, force the use of the low quality video stream from the Protect controller.

2. When all 3 of the above are unchecked, auto select video stream similar to how it currently works for the current triplet of force video stream quality options.

3. Make the original 3 only apply to **Low-Latency clients** and update the wording.

### Describe alternatives you have considered to the enhancement

As an alternative, just add a single extra checkbox instead of the 3 I proposed:
- [ ] When viewing livestreams **from High-Latency clients**, do **not** force the use of a specific quality video stream from the protect controller.