Fix time_frame for metrics
Summary
With instrumentation_class data merging to usage_data, we found metrics with Invalid time_frame, which may cause unexpected behavior to fail due to the amount of records in the defined period.
This issue is to fix those metrics
Monthly
https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210929103010_p_ci_templates_implicit_jobs_deploy_monthly.yml#L12
https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210929102736_p_ci_templates_implicit_jobs_deploy_latest_monthly.yml#L12
https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210929102434_p_ci_templates_implicit_jobs_build_monthly.yml#L12
https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216183203_product_analytics_test_metrics_union.yml#L12
https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216183652_bitbucket_server.yml#L12
https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216183648_github.yml#L12
https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216183650_bitbucket.yml#L12
Weekly
https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_7d/20210514013545_i_code_review_user_resolve_conflict_weekly.yml#L12
https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_7d/20210216181347_g_project_management_issue_cross_referenced_weekly.yml#L12
All
https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216174902_g_analytics_merge_request.yml#L12
Edited by Luis Mejia