set loggingConsumer after client initialization

Expected Behavior

We should be able to set a loggingConsumer on McpClient after querying its capabilities.

var capabilities = client.getServerCapabilities();
if (capabilities.logging() != null) {
    client.setLoggingLevel(McpSchema.LoggingLevel.INFO);
    client.setLoggingConsumer(consumer);
}

Current Behavior

Currently, we can set a loggingConsumer with McpClientTransport before client initialization. For example,

McpClient.sync(server.transport())
                .loggingConsumer(consumer)
                .build();

Context

However, many MCP servers' logging capabilities are not enabled. But we cannot query if the server has this capability before client initialization. Such a poor design makes it impossible to register a logging consumer safely.

Comienza leyendo la inicialización de McpClient y el flujo de consulta de capacidades; después, compáralo con la configuración de loggingConsumer de McpClientTransport. Verifica cómo se comportan setLoggingLevel y setLoggingConsumer antes de la inicialización. La tarea está terminada cuando se pueda registrar un consumer después de que getServerCapabilities() confirme la compatibilidad con logging, sin romper el uso existente del builder antes de la inicialización.