[Bug]: {info}/{note}/{warning}/{tip} and {expand} macros not converted by jira_to_markdown

[AnubhavSolanki]

Bug Description

JiraPreprocessor.jira_to_markdown converts the {panel} macro (added in #1052) but not the sibling panel-style admonition macros — {info}, {note}, {warning}, {tip} — nor the {expand} collapsible toggle. When issue text uses any of these, the macro tags leak through into the converted output as raw wiki markup (e.g. {info}...{info}, {expand}...{expand}), so the surrounded content is delivered wrapped in unconverted macros.

These are common in real issues: an {info} callout on a description, and an {expand} block wrapping generated metadata.

Steps to Reproduce

1. Have a Jira issue whose description uses, e.g.:

   {info:title=AUTO-GENERATED METADATA — DO NOT EDIT}...{info}
   {expand:Security MetaData}{code:json}{"kind":"not-fixable"}{code}{expand}
   

2. Fetch it via a tool that runs the description through jira_to_markdown (e.g. jira_get_issue).
3. Inspect the returned Markdown.

Expected Behavior

The macros are converted to Markdown, consistent with the existing {panel} handling:

• {info}/{note}/{warning}/{tip} → a labelled callout that preserves the macro type (info vs warning etc.) and the optional title.
• {expand} → a <details><summary> collapsible block, with inner content (including code blocks) preserved.

Actual Behavior

# jira_to_markdown output still contains raw macro tags:
{info:title=AUTO-GENERATED METADATA — DO NOT EDIT}...{info}
{expand:Security MetaData}...{expand}

mcp-atlassian Version

main (current)

Additional Context

{panel} handling was added in #1052; this is the same class of macro left unhandled. PR to follow.