Merge branch...

Merge branch '320782-add-deprecated-and-not_used-to-metrics-definitions-status-list-2' into 'master'

Add 'deprecated' and 'not_used' to metrics definitions status list

See merge request gitlab-org/gitlab!54960

config/metrics/schema.json

@@ -26,7 +26,7 @@
     },
     "status": {
       "type": ["string"],
-      "enum": ["data_available", "planned", "in_progress", "implemented"]
+      "enum": ["data_available", "planned", "in_progress", "implemented", "not_used", "deprecated"]
     },
     "milestone": {
       "type": ["number", "null"]

doc/development/usage_ping/metrics_dictionary.md

@@ -33,7 +33,7 @@ Each metric is defined in a separate YAML file consisting of a number of fields:
 | `product_group`     | yes      | The [group](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/data/stages.yml) that owns the metric. |
 | `product_category`  | no       | The [product category](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/data/categories.yml) for the metric. |
 | `value_type`        | yes      | `string`; one of `string`, `number`, `boolean`.                                                               |
-| `status`            | yes      | `string`; status of the metric, may be set to `data_available`, `implemented`. |
+| `status`            | yes      | `string`; status of the metric, may be set to `data_available`, `planned`, `in_progress`, `implemented`, `not_used`, `deprecated` |
 | `time_frame`        | yes      | `string`; may be set to a value like `7d`, `28d`, `all`, `none`. |
 | `data_source`       | yes      | `string`: may be set to a value like `database`, `redis`, `redis_hll`, `prometheus`, `ruby`. |
 | `distribution`      | yes      | The [distribution](https://about.gitlab.com/handbook/marketing/strategic-marketing/tiers/#definitions) where the metric applies. |