[Feat] Inspect Railway deployment runtime logs

[roomote-roomote]

​Opened on behalf of @mrubens. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

What changed

• Added a read-only get-deployment-logs Railway MCP tool alongside the existing account, project, and service inventory tools.
• Supports a direct deployment ID or resolves the latest deployment from project, service, and environment IDs.
• Bounds query inputs and returned log volume, redacts recognized credential patterns, and honors the existing deployment connection, task-run/auth-token, allowlist, and administrator-disabled-tool policies.

Why this change was made

Railway's hosted MCP does not expose a dedicated read-only runtime-log tool; log investigation is available only through a broad agent tool that is inappropriate for Roomote's restricted read-only surface. Railway's public GraphQL API exposes deployment-scoped runtime logs, allowing Roomote to add this capability without enabling speculative write operations.

Impact

Agents can inspect recent Railway runtime logs for a deployment or the latest deployment of a selected service while the existing Railway integration remains read-only. Existing whoami, list-projects, and list-services behavior is unchanged, and broad agent, deployment mutation, feature-flag mutation, and other write tools remain unavailable.

[roomote-community]

No code issues found. See task

_{Reviewed 9badc22}