Updating Respond Group GMAU

What does this MR do and why?

Updates Respond Group GMAU with additional actions that were available but not included, see Reevaluate Respond Group GMAU (gitlab-org/monitor/respond#145 - closed) for details.

Note:

An update like this to incident_management_total_unique_counts_weekly can cause inconsistent reporting of incident_management_total_unique_counts_weekly from older instances. This is due to the fact that new metric definition would only be available to instances that update to %15.5 or higher version (assuming that this MR lands in 15.5). So older instances would only report based on old definition, which might lead to confusing data

This means that unless instances update to %15.5, they will still be reporting on the old list of events based on the version that it was introduced to. It isn’t a breaking change, but important to remember when we’re looking at numbers for the aggregation metrics like incident_management_total_unique_counts_weekly that some of the data will be reporting from older definitions. We can address this by looking at adoption based on version to isolate the metric based on the same data definition.

Updates to monthly active users were done in a separate MR, Update config/metrics/counts_28d/20210216180622... (!101685 - closed).

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.