Lifecycle callbacks should be called in separate threads

[ChristopheCVB]

Describe the bug

Lifecycle callbacks should be called in separate threads

Code Sample

Simply add a Lifecycle callback when setting up the OBSRemoteController.

Expected behavior

In order to not to be blocked in our own thread, we should invoke callbacks in a separate thread.

Additional context

None.

[Blackn0va]

i need a change in the code here. The threads that are started from obswebsocket are never terminated, I can't terminate them in a hard way. This means that 24/7 stream bots will eventually run into the wall because there is no more memory available.