#30997 fix(mcp): OAuth authorize/register endpoints fail to resolve MCP server by server_id
## Bug Description
The OAuth broker endpoints (`/v1/mcp/server/oauth/{mcp_server_name}/authorize`, `/register`, `/token`, `/callback`) use `get_mcp_server_by_name()` to resolve the MCP server from the URL path parameter. However, the LiteLLM UI sends the **server_id** (SHA-256 hash) in the path — not the server_name or alias — causing the lookup to fail.
This results in: ```json {"detail": "MCP server authorization url is not set"} ```
## Root Cause
In `discoverable_endpoints.py`, the `authorize()` function (line ~535) and `register_client()` function (line ~999) both call:
```python mcp_server = global_mcp_server_manager.get_mcp_server_by_name( lookup_name, client_ip=client_ip ) ```
`get_mcp_server_by_name()` matches by alias → server_name → name, but **not by server_id**.
The UI constructs URLs like: ``` GET /v1/mcp/server/oauth/a1b2c3d4e5f6.../authorize ```
Where `a1b2c3d4e5f6...` is the `server_id` from `_generate_stable_server_id()`. Since this is a hash, it won't match any alias, server_name, or name.
Meanwhile, `get_mcp_server_by_id()` exists at line ~3365 in `mcp_server_manager.py` and correctly matches by `server.server_id`, but is never called in the OAuth fl…