Description

This PR implements a new Jira Service Management (JSM) connector, resolving the long-standing request in #2281.

While a standard Jira connector exists, it does not correctly handle Service Desk project types or JSM-specific API endpoints. This implementation creates a dedicated connector for JSM to allow indexing of tickets, requests, and comments from Service Desk projects.

Key Changes:

• Ported and cleaned up the logic from the stale PR #5392.
• Fixed the Icon Bug: Changed the Slack bot icon from .svg to .png to resolve the build failures that blocked the previous attempt.
• Frontend Config: Updated connectors.ts to match the latest frontend schema, ensuring the configuration form renders correctly.
• Backend Registry: Properly registered the connector in registry.py and constants.py.

Fixes #2281 Ref: #5392

How Has This Been Tested?

I have focused on fixing the configuration and build errors from the previous attempt:

• Static Analysis: Verified that connectors.ts configuration matches the frontend schema and compiles without errors.
• Bug Fix: Confirmed the icons.py logic now points to a valid .png resource (fixing the previous build failure).
• Unit Tests: Ported the test_jira_service_management_basic.py test suite. I am relying on the CI/CD pipeline to execute these tests in a clean environment to ensure no regressions.

/claim #2281

Summary by cubic

Adds a dedicated Jira Service Management connector to index Service Desk issues and comments. This closes #2281 and fills gaps the standard Jira connector couldn’t handle.

• New Features

  • New JSM connector with its own source type and backend registration.
  • UI config for base URL, scope (everything, project, or JQL), and comment email blacklist; plus source metadata and icon.
  • Basic tests covering source typing and JQL filtering.

• Bug Fixes

  • Slack bot uses a PNG icon for JSM to prevent build failures.

^{Written for commit 9636e9f6f9e735924228dc410dda407a88f05e36. Summary will update on new commits.}