Add per-project Jira resolution strategy

Allow configuring the Jira inbound Resolve action (resolution_strategy) per Sentry project instead of only organization-wide.

Current behavior

• Jira issue sync has a single org-level Resolve setting: Resolve / Resolve in Current Release / Resolve in Next Release (docs).
• That value is stored on the organization integration config and applied on inbound status sync via config.get("resolution_strategy") in sync_status_inbound.py.
• Per-project config today only covers outbound Sentry → Jira status mapping (IntegrationExternalProject resolved/unresolved statuses), not inbound resolution strategy (jira/integration.py).

Gap

Orgs with mixed release models cannot choose Resolve in Current Release for projects that regress on older builds without changing behavior for every project. Plain Resolve reopens issues when errors still fire on older releases.

Related

• Adjacent ask for FixVersion-based resolution: https://github.com/getsentry/sentry/issues/114208

Requested by Saad Khan via Junior.

--

View Junior Session in Sentry

Start with sync_status_inbound.py, where resolution_strategy is read from the organization integration config, and jira/integration.py, which currently handles per-project outbound status mapping. Trace how IntegrationExternalProject is configured and identify the relevant integration tests. Done means inbound Jira Resolve behavior can be selected per Sentry project while the existing organization-wide configuration remains supported.