Jira Connect descriptor vs Forge manifest use different issue panel URLs

Jira Connect descriptor (descriptor.py) uses /extensions/jira/issue-details/{issue.key}/ for the jiraIssueContexts web panel. Forge manifest (forge/manifest.yml) now correctly matches this path (PR #115603 fixed the legacy /issue/ path). Trap: looks like both should use the same URL since they serve the same panel, but they are separate integration paths (Connect vs Forge) with different routing. When modifying the issue panel URL, update BOTH files or the two integration modes will diverge. Also: use stable non-hashed CDN icon URLs (not content-hashed entrypoints) in the Forge manifest — hashed URLs break on redeploy. The unhashed path /_static/dist/sentry/entrypoints/logo-sentry.svg is served with cache-control: max-age=0, must-revalidate on sentry.io and is the correct stable URL for static manifests.