feat(api): add finding labels, finding URL and tenant info to Jira issues

send_findings_to_jira() now passes issue_labels (prowler, prowler-{provider},
prowler-{severity}, prowler-{check_id} and prowler-finding-{sanitized uid}),
a finding_url built from the new DJANGO_UI_BASE_URL setting (empty by
default, so self-hosted deployments emit no link unless configured) and the
tenant name as tenant_info. The label sanitizer is local to the API so it
does not depend on an unreleased SDK symbol.

docs/user-guide/tutorials/prowler-app-jira-integration.mdx

@@ -124,6 +124,16 @@ To manually send individual Findings to Jira:
 
     ![Send to Jira modal](/images/prowler-app/jira/send-to-jira-modal.png)
 
+### Finding Reference in the Jira Issue
+
+Every Jira issue created from a single Finding carries a stable reference back to that Finding, so issues can be filtered, searched with Jira Query Language (JQL), or matched by automation:
+
+* **Labels**: `prowler`, `prowler-<provider>`, `prowler-<severity>`, `prowler-<check-id>` and `prowler-finding-<finding-uid>`. Labels are sanitized deterministically: whitespace becomes `_`, control characters are removed, and values are truncated to Jira's 255-character label limit.
+* **Finding URL**: a link that opens the Finding in Prowler App, filtered by its unique identifier (UID) so it keeps working after later scans.
+* **Tenant Info**: the name of the Prowler organization that sent the Finding.
+
+Prowler Cloud always includes the Finding URL. In a self-hosted Prowler App, set `DJANGO_UI_BASE_URL` in the API environment (for example, `https://prowler.example.com`) to enable it. When the variable is empty, the issue is created without the link.
+
 ## Integration Status
 
 Monitor and manage your Jira integrations through the management interface: