fix(mcp): RequestPost fails with unknown field "id" in response

[electather]

Summary

When using the MCP server to add a request, the tool fails with:

RequestPost failed: ... (HTTP json: unknown field "id")

Likely the same root cause as #93 (WatchlistPost unknown field "id").

Steps to Reproduce

Use the MCP RequestPost tool to request a movie (e.g. Spiderhead, tmdbId: 615469, mediaType: movie).

Expected Behavior

The request is created successfully.

Actual Behavior

The tool returns an error: HTTP json: unknown field "id".

The Overseerr API responds with a full request object containing "id", "createdAt", "updatedAt", nested "media" (with its own "id"), "requestedBy", "modifiedBy", etc. — but the Go client model used to deserialize the response is missing these fields.

Example API response snippet:

{
  "type": "movie",
  "media": { "id": 36, ... },
  "requestedBy": { "id": 1, ... },
  "modifiedBy": { "id": 1, ... },
  "status": 2,
  "is4k": false,
  "id": 32,
  "createdAt": "2026-03-18T23:06:01.738Z",
  "updatedAt": "2026-03-18T23:06:01.738Z"
}

Root Cause (suspected)

Same as #93 — the generated pkg/api response model for RequestPost is missing fields present in the actual API response. The strict JSON decoder rejects unknown fields instead of ignoring them.

The fix likely involves regenerating pkg/api from an updated open-api.yaml that accurately reflects the full response shapes for both WatchlistPost and RequestPost.