feat: Migrate Jira client to Cloud API v3

[r-pedraza]

Pull Request

📝 Summary

This pull request migrates the Jira network client from using the deprecated v2 API to the current Jira Cloud REST API v3. This change is necessary to maintain compatibility with modern Jira Cloud instances. The update includes switching to Basic Authentication and adjusting API endpoints.

🔧 Changes Made

• Updated the authentication method from Bearer Token to Basic Auth (using email:api_token), as required by the Jira Cloud API.
• Changed the API base path in JiraNetwork from /rest/api/2 to /rest/api/3.
• Modified the issue search endpoint in IssueService from search to search/jql to align with API v3 standards.
• Updated unit tests for JiraNetwork to validate the new Basic authentication header format.

🧪 Testing

• Unit tests added/updated (poetry run pytest)
• All tests passing (make test)
• Manual testing with titan-dev

The unit test test_network_builds_correct_auth_header was updated to verify that the Authorization header is correctly formatted for Basic Auth using a base64-encoded email and API token.

📊 Logs

• No new log events

✅ Checklist

• Self-review done
• Follows the project's logging rules (no secrets, no content in logs)
• New and existing tests pass
• Documentation updated if needed

[finxo]

plugins/titan-plugin-jira/titan_plugin_jira/workflows/analyze-jira-issues.yaml (line 14):
The workflow advertises query_name as an overridable top-level param, but this step still hardcodes query_name: "open_issues", so any caller-supplied value is ignored. Evidence:

params:
  query_name: "open_issues"
...
steps:
  - id: search_open_issues
    params:
      query_name: "open_issues"

Please wire the step to the workflow param instead of hardcoding the value, otherwise the documented override does not work.