AddCallToolFilter does not allow to catch exceptions

[gophph]

Describe the bug
AddCallToolFilter does not allow to handle exception as exception is getting handled and suppressed inside next filter

To Reproduce
Steps to reproduce the behavior:

1. Use following code described in filters.md to handle exception

 services
 .AddMcpServer()
 .AddCallToolFilter(next => async (context, cancellationToken) =>
 {
 try
 {
 var result = await next(context, cancellationToken);
 return result;
 }
 catch (Exception ex)
 {
 return new CallToolResult
 {
 Content = [new TextContentBlock { Type = "text", Text = $"Error: {ex.Message}" }],
 IsError = true
 };
 }
 })
 .WithHttpTransport()
 .WithToolsFromAssembly();

2. Don't configure other filters
3. Make call of a tool that throws an exception
4. Observe result object containing CallToolResult object with
   IsError = true,
   Text = "An error occurred invoking '<redacted>'."
   and no exception thrown to catch

Expected behavior
I should be able to handle exception and build my custom CallToolResult

Logs
n/a

Additional context
Version: 0.4.0-preview.1

[Jaben]

Right? The exception handler should be LOW level filter -- not the "FINAL" filter configured above all others. We should be able to override with our own exception handling.

[wrobtom]

Tagging @halter73 as filters were introduced in #733.
Are there any plans to fix this in near future to match asp.net core middleware/filters behavior for exceptions?

[halter73]

Thanks for the bug report. #844 should fix it so all exceptions propagate through tool call filters.