Support resolving Issues for multiple release versions

#### Description

Currently, Sentry allows resolving Issues for a single release version. In some workflows, however, the same Issue may affect multiple release branches or product versions, and fixes may be applied to one or several of these versions independently.

It would be useful to support resolving an Issue against multiple release versions to accurately reflect where the fix has been applied.

#### Use cases

- Mark an Issue as resolved for several releases where the fix was deployed.
- Improve tracking of which versions still contain the issue and which don't.
- Allow triage teams to better manage multi-version release lines.

#### Proposal

- Extend the resolve functionality to allow selecting multiple release versions.
- Expose this capability via both the UI and API.

#### Benefit

This would allow teams managing multiple release branches to more accurately track resolution status across versions, reducing confusion and improving incident management for multi-version products.

No files, tests, or entry points are named. Start by locating the existing single-release resolution flow in the UI and API, then determine how resolution by release is represented and exposed. Done means users can select multiple releases and the issue accurately reports which versions are resolved.

Written by the indexing model from the issue text.