ref(ACI): Remove workflow_status_update_handler and use generic handler

[saponifi3d]

Description

Create a generic activity_handler handler for activity updates. This will allow us to have a single hook for activities, but for now it will only handle the resolved activities.

This should also fix the issue where only metric issues were getting a resolution case, as this is a more generic call site.

[Christinarlong]

is the goal to get rid of group_status_update_registry? If so, I'm curious why? I'm not familiar with the original purpose of the registry so prob. missing context here

[saponifi3d]

yep! that's the goal. (the next PR in the stack, remove status handler, will do that if you're curious what that will look like).

there are two main reasons:

1. the way the group_status_update_registry works right now is that it will read from the kafka consumer, then trigger for activities. unfortunately, only metric issues really create activities like this. that means that if a SET_RESOLVED activity happens on a cron issue, it won't trigger workflow engine or send notifications to users about that resolution. The generic handler based on the activity (instead of the status change message) will be triggered for all those missing activities 🎉

2. there are two different registries for more or less 1 code path, we want to trigger the process_workflow_activity method. This will allow us to reduce the total number of registries. Since the group_status_update_registry was more different than the desired goal, i decided to give that one the chop instead of the seer one.

[owen-sheppard]

I'm trying to use the uptime monitor and am not receiving a resolved webhook. Is this issue fixed?