[D+ Issues] allow setting the issue status when creating it (#23555)

Update the `createIssue` mutation to allow you to set the status the Issue should be created with. I'm doing a workaround in the "compass propose issues" job to set the status after the issue is created, but that seems to get unauthorised errors frequently (not sure why, still investigating). Regardless, being able to set the status of the issue when creating it makes sense, so let's do that.

The status defaults to OPEN so we shouldn't need to update the FE. I do expose the option to the MCP server and the `dg cli` so that those surfaces have this capability

Internal-RevId: 226123a0f6002fd2bc1479b0765c31428cee6500

Author: jamiedemaria

skills/dagster-expert/skills/dagster-expert/references/cli/api/issue/INDEX.md

@@ -35,19 +35,20 @@ The response will contain a list of `limit` Issues in chronologically descending
 ## Create a Dagster Plus Issue
 
 ```bash
-dg api issue create --title <title> --description <description>
+dg api issue create --title <title> --description <description> --status <status>
 ```
 
 - `<title>` - The title should be short and clearly state the problem to fix so that the reader quickly understands the cause of the problem. Do not mention specific run ids or other downstream impacts.
 - `<description>` - The description should be a total of 2-4 bullet points that outline the root cause of the problem and next steps.
+- `--status` (optional) - updates the status of the Issue. One of `OPEN`, `CLOSED`, `TRIAGE`, `CANCELED`
 
 ## Update a Dagster Plus Issue
 
 ```bash
 dg api issue update <ID>
 ```
 - `<ID>` - The ID of the Issue to update
-- `--status` (optional) - updates the status of the Issue. One of `OPEN`, `CLOSED`, `TRIAGE`
+- `--status` (optional) - updates the status of the Issue. One of `OPEN`, `CLOSED`, `TRIAGE`, `CANCELED`
 - `--title` (optional) - updates the title of the Issue
 - `--description` (optional) - updates the description of the Issue
 - `--context` (optional) - replaces the additional context stored about this Issue. If you want to append to the current context, fetch the Issue first, append to the context string with the new information, then call the `update` command with the resulting context.