Fix: Scope authorization header examples to WSO2 IS <= 7.2.0 in custom SMS provider docs

[Copilot]

Authorization header examples in the custom SMS provider "Headers" field are only relevant for WSO2 Identity Server <= 7.2.0, which lacks a dedicated Authentication field in the UI. Versions > 7.2.0 and Asgardeo expose a dedicated authentication configuration, making the auth header guidance unnecessary and potentially confusing.

Changes

• en/includes/guides/notification-channels/configure-sms-provider.md
  • Wrapped the authorization-specific description text and examples (Basic auth, ****** multiple headers) in a Jinja2 conditional: {% if product_name == "WSO2 Identity Server" and is_version <= "7.2.0" %}
  • For all other versions, the Headers field shows a generic header example (x-api-key: your_api_key) without auth-specific guidance

Related PRs

Test environment

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines?
• Ran FindSecurityBugs plugin and verified report?
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets?

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}