Expose quote_body, signature_id and should_add_default_signature in MCP create_draft / update_draft - and add forwarding

When Claude creates a reply draft through the Front MCP server, the draft contains only the body text - no quoted thread history and no signature. Front's own Reply button adds both.

The Core API already supports this. POST /conversations/{id}/drafts accepts quote_body, signature_id and should_add_default_signature. The MCP create_draft and update_draft tools expose none of them, so an AI-created draft can never match what Front itself produces.

Separately, there is no way to create a forward at all: no forward endpoint exists in the Core API, only in the Plugin SDK (Front.forward() / replyOptions.type: "forward"), which requires a plugin running in the Front UI.

Impact: I have to re-add the quoted history and my signature by hand on every AI-drafted reply. The manual rework defeats the purpose of the integration - it is faster to skip the connector and hit Reply.

Asks: (1) expose quote_body, signature_id and should_add_default_signature in create_draft and update_draft, ideally with quoting and the default signature applied automatically on a reply - opt-in behind a parameter is fine if you do not want to change the current default of should_add_default_signature=false; (2) add forwarding to the Core API and the MCP server, or document a supported workaround.