Please address the comments from this code review:

## Overall Comments
- The Jira helper functions build JSON payloads via heredocs with unescaped interpolated values (e.g., JQL in `get_issues`, `COMMENT` in `comment_on_issue`), which will break if those contain quotes or newlines; consider constructing the JSON with `jq -n --arg` or otherwise escaping these fields properly.
- `get_issues`/`comment_on_issue` write to a fixed `/tmp/request.json` path, which can cause races or interference if multiple scripts or steps call these in parallel; using `mktemp` to create a unique temporary file per call would make this more robust.
- In `get_issues`, `PAGE_SIZE` and `next_page_token` are implicitly global; making them `local` would reduce the risk of side effects if the script grows or additional functions reuse these names.

## Individual Comments

### Comment 1
<location path=".github/workflows/scripts/common.sh" line_range="111" />
<code_context>
+    while true; do
+        cat <<EOF > /tmp/request.json
+{
+    "jql": "$JQL",
+    "maxResults": "${PAGE_SIZE}",
+    "nextPageToken": "${next_page_token}",
</code_context>
<issue_to_address>
**issue (bug_risk):** JQL is interpolated into JSON without escaping, which can break the request for certain characters.

If `JQL` ever includes double quotes, backslashes, or newlines (e.g., from future changes or dynamic input), this here-doc will produce invalid JSON and the Jira request will fail in a hard-to-diagnose way. Consider instead:
- building the payload with `jq` (e.g., `jq -n --arg jql "$JQL" '{jql: $jql, ...}'`), or
- JSON-escaping `JQL` first (e.g., `JQL_ESCAPED=$(printf '%s' "$JQL" | jq -Rs .)` and embedding that).
This makes the helper resilient to JQL contents and future changes.
</issue_to_address>

### Comment 2
<location path=".github/workflows/scripts/common.sh" line_range="189" />
<code_context>
+                "content": [
+                    {
+                    "type": "text",
+                    "text": "${COMMENT}"
+                    }
+                ]
</code_context>
<issue_to_address>
**issue (bug_risk):** COMMENT is inserted into JSON without escaping, which can break the payload or cause malformed comments.

Since COMMENT may contain quotes, backslashes, or newlines (e.g., multi-line instructions), interpolating it directly into the JSON can produce invalid JSON or change the structure. Escape COMMENT as JSON before embedding, for example:

```bash
COMMENT_JSON=$(printf '%s' "$COMMENT" | jq -Rs .)
cat <<EOF > /tmp/request.json
{
  "body": {
    "version": 1,
    "type": "doc",
    "content": [
      {
        "type": "paragraph",
        "content": [
          {
            "type": "text",
            "text": $COMMENT_JSON
          }
        ]
      }
    ]
  }
}
EOF
```

This ensures the JSON remains valid regardless of COMMENT’s contents.
</issue_to_address>