Support Jira Server/DC and split-host Confluence deployments

[ucchishta-dd]

Summary

I found several assumptions in the CLI that break Jira Server/Data Center and deployments where Jira and Confluence do not share the same host or credentials.

Repro / findings

Jira

• Jira core endpoints are hardcoded to Cloud-style /rest/api/3/... paths in several places.
• This breaks Server/DC, where /rest/api/2/... is typically required.
• There is no runtime override for Jira REST version selection.

Confluence

• Confluence commands assume ATLASSIAN_URL is also the Confluence host.
• Confluence commands also assume Jira and Confluence share the same credentials.
• This breaks split-host or split-credential setups.

Formatting

• Confluence search result URLs are hardcoded to .atlassian.net.
• Confluence page URLs assume /wiki.
• Jira issue formatting assumes description is always a string, but Cloud often returns ADF objects.

Proposed fixes

• Add a Jira API version override, e.g. ATLASSIAN_JIRA_API_VERSION=2|3|latest.
• Use Jira Server/DC-compatible endpoints when appropriate.
• Add CONFLUENCE_URL with fallback to ATLASSIAN_URL.
• Add CONFLUENCE_USERNAME and CONFLUENCE_API_TOKEN with fallback to the Atlassian vars.
• Generate Confluence URLs from configured host/base path instead of hardcoded .atlassian.net or /wiki.
• Make Jira issue description formatting handle both string and ADF content.

I can open a PR with these changes.