Improve stream privacy interactions on the Live View page

[CDx4f3kCAf3Y]

Tested in commit b624c98.

Being able to disable a stream from the Live View page and the quick Disable/Enable buttons on the Stream page are good.

However, there needs to be a way to distinguish between having administratively disabled a stream and disabling a stream for privacy.

The thought here is that:

• In the former case, this would be a more long term / permanent type operation.
• In the later case, (especially when toggled from the Live View page) it would be a short term / temporary type operation.

The mechanism to disable the stream from the Live View page worked well. I was, however, surprised to find the stream gone when I went back / reloaded the Live View page later. I was expecting the steam to still be on that page and in it's disabled status, waiting for me to re-enabled it.

I would recommend:

• Add a 'privacy' flag to the Streams database table.
• Update the Live View page to say 'Pause stream for privacy'.
  • When clicked, it sets the privacy flag true and leaves the enabled flag untouched.
  • In the backend, the final effect is the stream is disabled (enabled === false || privacy === true) but from the frontend it is treated as temporary.
• Update the Live View page to show all enabled streams, but show an overlay on the privacy enabled streams similar to the overlay displayed when the 'Pause stream for privacy' button is clicked.
• When a button on that overlay is clicked, the privacy flag is disabled and the stream resumes seamlessly.

[matteius]

Changes pushed.