Version Header in APIM is unable to understood by MCP.

Issue: When we have multiple versions of single api, Eg: Contoso API - v1, v2, v3. These are having base url same. Only difference is the version header we pass.
Request Header -
APIM-API-Version: v1 - calls the Contoso API-v1.
APIM-API-Version: v2 - calls the Contoso API-v2.
similarly v3 calls v3.
If user doesn't pass this header when calling this api, it will get 404 error. expected behavior from APIM perspective.

When an MCP server is made out of Contoso API-v2. The custom header we tried pass at mcp configuration. something like below -
```
"my-mcp-server-contoso-v2": {
"url": "https://contoso-apim-uat.azure-api.net/contoso-v2/mcp",
"type": "http",
"headers": {
"APIM-Api-Version":"v2",
"Ocp-Apim-Subscription-Key": "1***********2"
}
}
```

but it throws 404 error when trying to get response for a prompt.. Can anyone help with this?