feat: Add docling-mcp in the distribution

[dolfim-ibm]

1. Add docling-mcp in the container image
2. Upgrade packages

Running Docling MCP will be possible via

podman run -p 8000:8000 quay.io/docling-project/docling-serve -- docling-mcp-server --transport streamable-http --port 8000 --host 0.0.0.0

[github-actions]

✅ DCO Check Passed

Thanks @dolfim-ibm, all your commits are properly signed off. 🎉

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

• title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?(!)?:

[RitchieMatt]

I really wish that MCP in the docker-serv was an option.
I've tried various means that have absorbed the bulk of the day.

If any one has a solution that is viable for having a 'docling-serv' that also has the 'docling-mcp', such that we can use either the UI, the API, or the MCP. Please let me know.
I've focused on configuring a good stable 'docling-serv' to faciliate 'docling-mcp' via streaming http.
I understand that this "should" be part of the new release 1.1.0.
I can't get it to work as an MCP server for VSCode; Roo Code, or Kilo Code, or VSCode MCP

Here is the condensed report from hours of sessions and multiple token burns, that hurt:

# Docling MCP Integration Session Report - FAILURE

## Executive Summary
**RESULT: COMPLETE FAILURE** - After extensive troubleshooting, the docling MCP server remains inaccessible through the MCP system despite appearing to work at the protocol level.

## What Was Attempted (And Failed)

### 1. Transport Protocol Investigation ❌
- **Attempted**: Changed from `sse` to `streamable-http` to `stdio` transports
- **Result**: Transport changes were applied but didn't resolve the core issue
- **Status**: Docling MCP server responds to HTTP requests but not accessible via MCP tools

### 2. Endpoint Discovery ❌  
- **Attempted**: Tested various endpoints (`/`, `/mcp`, `/sse`)
- **Result**: Found `/mcp` endpoint responds with proper MCP protocol messages
- **Status**: HTTP connectivity works, MCP integration does not

### 3. Configuration Changes ❌
- **Attempted**: Multiple modifications to `.roo/mcp.json` configuration
- **Result**: Configuration appears correct but server not recognized by MCP system
- **Status**: Configuration matches working servers but docling not available

### 4. Container Restart Cycles ❌
- **Attempted**: Multiple container restarts, rebuilds, and configuration reloads
- **Result**: Container runs successfully, both services active, but MCP integration fails
- **Status**: Infrastructure working, integration broken

## Current State (UNCHANGED FROM START)

### What's Working ✅
- Docling container running at `10.0.0.24`
- Docling-serve REST API accessible at `http://localhost:8024/docs`
- Docling-mcp-server process running (PID 9)
- HTTP endpoint responding at `http://localhost:8025/mcp`
- MCP protocol messages being exchanged (200 OK, 202 Accepted responses)

### What's Broken ❌
- **Docling MCP server NOT visible in available MCP servers list**
- **Cannot execute MCP tools** - "Not connected" error
- **MCP integration completely non-functional**

## Root Cause: UNKNOWN
Despite extensive investigation, the fundamental issue remains unidentified:
- HTTP connectivity: ✅ Working
- MCP protocol responses: ✅ Working  
- Container processes: ✅ Working
- Configuration syntax: ✅ Correct
- **MCP system recognition: ❌ FAILING**

## Technical Evidence of Failure
```bash
# MCP server test - FAILS
use_mcp_tool(server_name="docling", tool_name="list_supported_formats")
# Error: "Not connected"

# Available MCP servers - docling MISSING
time, Context7, postgres, git, tavily, n8n-mcp, sequentialthinking
# docling: NOT PRESENT

Wasted Effort Summary

• 2+ hours of troubleshooting
• Multiple transport protocol changes
• Countless container restarts
• Configuration file modifications
• Protocol-level testing
• Zero functional progress

Conclusion

This session achieved ABSOLUTELY NOTHING. The docling MCP server integration remains completely broken with no clear path to resolution. The issue appears to be a fundamental incompatibility or system-level problem that cannot be resolved through configuration changes or container restarts.

Recommendation: Abandon this approach and investigate alternative integration methods or seek expert assistance with MCP system internals.