Sentry Automatically Closing Issues on Azure DevOps "Resolved" State Instead of "Closed"

### Environment

SaaS (https://sentry.io/)

### Steps to Reproduce

The customer configured their Sentry integration with Azure DevOps to automatically close Sentry issues when the corresponding DevOps ticket reaches the "Closed" state.

However, upon setting a DevOps ticket to "Resolved" (which is the state before "Closed"), Sentry incorrectly closed all the connected Sentry issues. This behavior is unexpected, as the integration is only supposed to close connected issues when the DevOps ticket reaches the "Closed" state.

Please find additional information in the internal ticket.

### Expected Result

Sentry should only close the connected issues when the DevOps ticket reaches the "Closed" state.

### Actual Result

Sentry automatically closed all connected issues as soon as the DevOps ticket was set to "Resolved," even though the ticket was not yet "Closed."

### Product Area

Settings - Integrations

### Link

_No response_

### DSN

_No response_

### Version

_No response_

┆Issue is synchronized with this [Jira Improvement](https://getsentry.atlassian.net/browse/FEEDBACK-2328) by [Unito](https://www.unito.io)