Fix bug in `usage_activity_by_stage_monthly.manage.groups_with_event_streaming_destinations`

Summary

Complete details can be found in this issue. In short, a Service Ping metric has the wrong filter applied to it, and we need it to be fixed.

Steps to reproduce

1. Download Service Ping SQL queries
2. Look for usage_activity_by_stage_monthly.manage.groups_with_event_streaming_destinations

Example Project

What is the current bug behavior?

Filtered down to "namespaces"."created_at" BETWEEN '2022-06-28 18:42:30.126396' AND '2022-07-26 18:42:30.126433'

What is the expected correct behavior?

It should be filtered down to "audit_events_external_audit_event_destinations"."created_at" BETWEEN '2022-06-28 18:42:30.126396' AND '2022-07-26 18:42:30.126433'

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes

Remove this metric as it is broken and not used #369871 (comment 2223360853)