Fix Bot API 10.3 parameters and nested multipart uploads

[saind-sangwin]

The registry already lists all 185 Bot API methods, but Bot API 10.3 parameters can be missing or silently dropped, and files nested in documented input objects are not consistently uploaded. This change aligns all 932 top-level parameter entries with the current specification and derives multipart traversal from Telegram's input types.

• Add missing parameters, remove obsolete ones, correct requiredness, and allow empty draft text. Reject unknown parameters consistently in standard and meta modes.
• Upload files in profiles, stories, stickers, polls, paid media, live photos and recursive rich-message blocks using generated file-field schemas. Isolate concurrent URL downloads and clean up temporary files.
• Return complete responses by default with opt-in truncation. Add method-search pagination and complete parameter discovery.
• Refresh the official documentation snapshot, audit requiredness and upload-schema drift, and add audit:live. Document the scope of the coverage claim in COVERAGE.md.

Validation: 293 tests passed, including registry checks for all 185 methods and in-memory MCP client/server tests that inspect outgoing HTTP bodies. Type checking, lint, build, saved-spec audit and live Bot API 10.3 audit passed. These checks use mocked Telegram responses; they do not claim successful live execution of every payment, gift, administrative or business operation.

The MCP SDK minimum is raised to 1.29.0 so registered tools preserve full Zod object validation. Package versions are left for the maintainer's release process.