update_issue with status: ignored defaults to archived_forever instead of archived_until_escalating #878
Description
When calling update_issue with status: "ignored", Sentry sets the substatus to archived_forever rather than archived_until_escalating.
There is no way to pass statusDetails: { ignoreUntilEscalating: true } through the tool, making it impossible to archive an issue until it escalates via MCP — it has to be done manually in the UI.
Expected: status: "ignored" should default to archived_until_escalating (matching Sentry UI default behavior), or the tool should expose a parameter to control this.