bug: serverInfo.version reports the FastMCP version instead of kubeflow-mcp's

### Description

`initialize` returns `serverInfo.version` as `3.4.4`, which is the installed FastMCP version. kubeflow-mcp itself is `0.1.1`, as in `kubeflow_mcp.__version__` and `server.json`. Clients and debug output show the wrong version. I'll open a PR for this.

### Steps to Reproduce

1. Run `kubeflow-mcp serve --transport stdio`
2. Send `initialize` from any MCP client
3. Read `serverInfo.version` in the result

### Expected Behavior

`0.1.1`, matching `kubeflow_mcp.__version__`.

### Actual Behavior

`3.4.4`.

### MCP Server Version

main (467348f)

### Python Version

3.12

### Kubernetes Version

n/a, no cluster needed

### MCP Client

a raw stdio client and FastMCP's in-memory `Client`

Start with the initialize handler and compare its serverInfo.version source with kubeflow_mcp.__version__ and server.json. Reproduce the response using kubeflow-mcp serve --transport stdio or FastMCP's in-memory Client, then verify that initialize reports 0.1.1 instead of 3.4.4.

Written by the indexing model from the issue text.