Fix Issue update flow to prevent redoing actions

[ykamo001]

When Issues are attempted to be updated, we should do a no-op if the action does not actually change anything. Look into update_group function and entry path where we call update_groups from sentry.api.helpers.group_index. This function currently allows a resolved issue to be resolved again, or an archived issue to be archived again, resulting in multiple of the same activity to be created in the activity model.

[getsantry[bot]]

Routing to @getsentry/product-owners-issues for triage ⏲️

[mrduncan]

Added to the Core Product rotational backlog, we'll look into potentially resolving this as a part of upcoming work to the issue stream since it also seems to be one of the places allowing duplicate resolutions.

[ykamo001]

Related to: https://github.com/getsentry/sentry/issues/69252