More input options to STT

[cdusold]

I stream with friends often and would like to open the discord chat to STT for talking to the buddies. This likely will be unusable until #19 is implemented.

• Having the ability to capture individual program audio outputs is one option, and would enable more generic use of this. OBS's Application Audio [Output] Capture is sort of the idea I had.
• Something similar to the Discord Reactive Images stuff would be good too, as it would be able to tell individual voices and label the inputs with names from the Discord server.
• Maybe a webhook websocket client or eventbus message digestion (like eventSub for Twitch is) access to the STT? Some externally callable API? That could let us leave it to plugin authors to do the heavy lifting.

[WhiskerWeirdo]

The last item is a no-go from a design standpoint. While BBB itself uses external API's en services like Twitch, Azure, OpenAI, etc. I do not want webhook integration functionality exposed from the application itself. The whole point I disliked from JJ is that you are reliant on an external service for the basic functionality of the application to work.

BBB is a local running client-program; so websocket client or eventbus message digestion (like eventSub for Twitch is) are within design boundaries.