Declaring capability to send resource notifications disables resource templates added with WithResources

[mikekistler]

Describe the bug

In an MCP Server, if the server is created with the options to declare support to send resource notifications

builder.Services.AddMcpServer(
    options =>
        // Declare support for sending resource subscription notifications
        options.Capabilities = new()
        {
            Resources = new()
            {
                Subscribe = true,

            }
        }
    )
    .WithHttpTransport()
    .WithResources<LiveResources>();

the resources added using WithResources are not exposed to the client.

Removing the options => ... from the AddMcpServer parameters results in the resources being exposed but then the capability is not declared to the client.

To Reproduce

I can share a project that repros the problem if needed.

Expected behavior

I should be able to declare support for resource subscriptions and still use WithResources to expose resources.

[halter73]

#656 is a different issue but also related to how we wire up resources when you use both WithResources and WithSubscribeToResourcesHandler. This issue adds manually setting the resources capability into the mix which is definitely worth considering when we try to fix the WithSubscribeToResourcesHandler issue. Hopefully we can fix both of these issues together.