fix(reporting/jira): match status-not against transition target status name

## Summary This issue tracks the bug fixed in PR #7361 by @knakul853. ## Problem In `CloseIssue` (pkg/reporting/trackers/jira/jira.go), the code built a JQL clause using `StatusNot` as a status name (`status != "<StatusNot>"`) but then compared `StatusNot` against `transition.Name` when selecting the transition to invoke. Because `StatusNot` is a **status name** (populated from Jira project statuses, declared as `yaml:"status-not"` / `json:"status_not"`), workflows where transition names differ from their target status names caused the transition lookup to fail silently — no API call, no error, no log. Default Atlassian workflows were unaffected because transition names often equal target status names. Custom workflows with diverging transition/status names were broken. ## Fix Compare `StatusNot` against `transition.To.Name` (the transition target status name) instead of `transition.Name`. ## References - PR: https://github.com/projectdiscovery/nuclei/pull/7361 - Comment: https://github.com/projectdiscovery/nuclei/pull/7361 ## Requested by @Mzack9999