Fix MDX verification failures in i18n files due to Callout indentation

[Copilot]

✨ Summary

MDX verification was failing for 6 translated files due to incorrect indentation inside <Callout> tags. The MDX parser requires specific indentation patterns that differ from standard markdown formatting.

Files affected:

• src/i18n/content/{es,fr,jp,kr,pt}/docs/alerts/get-notified/notification-integrations.mdx
• src/i18n/content/pt/docs/cci/configure-cci/general-setting.mdx

Root cause: Translated files used consistent 6-space indentation for all content inside Callout tags, but the MDX compiler expects the pattern used in English source files:

• 6 spaces before <Callout>
• 1 space before heading text
• 18 spaces before bullet lists
• 0 spaces before </Callout>

Changes:

• Matched Callout indentation patterns to English source files
• Removed blank lines between Callout headings and content where present

All files now pass yarn verify-mdx.

🖼️ Screenshots

N/A

🔮 Engineering checklist

• [x] Code changes are self-documenting or clearly commented/documented
• [x] No new warnings or errors where added to the browser or build console

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.