Client.cs patch - Fixes Connect() not returning callback result when the socket isn't null

[BlueWaterCrystal]

Fixes Connect() not returning callback result when the socket isn't null.

What kind of change does this PR introduce?

Added callback?.Invoke(this); to Connect() in Client.cs

What is the current behavior?

ConnectAync() hangs when Connect() doesn't return a callback result.

Which is also used by supabase-csharp - client.InitializeAsync();

supabase-community/supabase-csharp#60

What is the new behavior?

Connect() invokes the callback and then returns.
ConnectAync() Doesn't get stuck when the socket isn't null.

Additional context

This issue was introduced in 5.0.2, I believe before the result was created using TrySetResult() istead of SetResult Callback.

[acupofjose]

Great catch - thanks so much for taking the time to debug this for us!