Improve cancellation token handling in Utilities.cs (#331)

A using statement was added to ensure proper disposal of the CancellationTokenSource. Additional error handling was also included to catch an OperationCanceledException and prevent it from causing unintended side effects. The client response is now properly disposed in the finally block.

SharedLibraryCore/Utilities.cs

@@ -1386,16 +1386,21 @@ public static async Task<string> PromptClientInput(this EFClient client, string
                 IGameEventSubscriptions.ClientMessaged += OnResponse;
                 await client.TellAsync([prompt], token);
 
-                var tokenSource = new CancellationTokenSource(DefaultCommandTimeout);
+                using var tokenSource = new CancellationTokenSource(DefaultCommandTimeout);
                 using var linkedTokenSource = CancellationTokenSource.CreateLinkedTokenSource(tokenSource.Token, token);
 
                 clientResponse.Wait(linkedTokenSource.Token);
 
                 return response;
             }
+            catch (OperationCanceledException)
+            {
+                return null;
+            }
             finally
             {
                 IGameEventSubscriptions.ClientMessaged -= OnResponse;
+                clientResponse.Dispose();
             }
 
             async Task OnResponse(ClientMessageEvent messageEvent, CancellationToken cancellationToken)
@@ -1409,6 +1414,7 @@ async Task OnResponse(ClientMessageEvent messageEvent, CancellationToken cancell
 
                 if (await validator(response))
                 {
+                    // ReSharper disable once AccessToDisposedClosure
                     clientResponse.Set();
                 }
                 else