[ISSUE] Give users the opportunity to handle "Unsupported events" rather than just throwing them away

[DrEsteban]

Issue Type

• Feature Request

Describe the issue

obs-websocket-dotnet/obs-websocket-dotnet/Events.cs

Lines 522 to 526 in b8ae595

	default:
	var message = $"Unsupported Event: {eventType}\n{body}";
	Console.WriteLine(message);
	Debug.WriteLine(message);
	break;

Right now the library has a default: case when handling events that simply throws unrecognized events away, with no ability to intercept them. The library should provide a better mechanism for users to handle this differently/extend the capability of the library if they wish.

To Reproduce
N/A

Expected behavior
The library should provide a better mechanism for users to handle this differently/extend the capability of the library if they wish.

Screenshots
N/A

Versions
Latest, as of 5/21/2024

Additional context
This flow is being triggered in the context of creating new input sources in OBS. I'm not sure what the unsupported event is that's coming through, but just calling out that it's a supported scenario in the library.