Analyze usage ping on 13.0

Description

This is a followup for https://gitlab.com/gitlab-org/gitlab/-/issues/208233

Dashboard:

https://app.periscopedata.com/app/gitlab/632033/WIP:-Usage-Ping-QA

Issues

Parent Issue: https://gitlab.com/gitlab-org/telemetry/issues/308

Continuation of #205281 (closed)

Pings

Usage ping for 2020-04-

Check 0: ingress_modsecurity

          ingress_modsecurity_logging: distinct_count(successful_deployments_with_cluster(::Clusters::Applications::Ingress.modsecurity_enabled.logging), column),
          ingress_modsecurity_blocking: distinct_count(successful_deployments_with_cluster(::Clusters::Applications::Ingress.modsecurity_enabled.blocking), column),
          ingress_modsecurity_disabled: distinct_count(successful_deployments_with_cluster(::Clusters::Applications::Ingress.modsecurity_disabled), column),
          ingress_modsecurity_not_installed: distinct_count(successful_deployments_with_cluster(::Clusters::Applications::Ingress.modsecurity_not_installed), column)

Check 1: Jira import State

!29925 (merged)

      jira_label = create(:label, project: projects[0])
      create(:jira_import_state, :finished, project: projects[0], label: jira_label, failed_to_import_count: 2, imported_issues_count: 7, total_issue_count: 9)
      create(:jira_import_state, :finished, project: projects[1], label: jira_label, imported_issues_count: 3, total_issue_count: 3)
      create(:jira_import_state, :finished, project: projects[1], label: jira_label, imported_issues_count: 3)
      create(:jira_import_state, :scheduled, project: projects[1], label: jira_label)

Check 2: Move container_expiration_policies_usage to counts

!31470 (merged)