Add count_weekly, settings, license top level keys to usage data

Part of https://gitlab.com/gitlab-org/telemetry/-/issues/403#proposal

See !41883 (comment 414704788)

From @jeromezng

Are count_all, count_28d, count_7d new columns in version-app?

Yes we'll need these columns added

Should we have the category in this json? I mean category defined in know_event.yml

I prefer trying to keep this as flat as possible and instead to add details into the naming convention.

--

How about something like this?

Metric and Event Name:

• top_level: count_7d, count_28d, count_all, license, setting
• segmentation: group, project, user, none
• event_name: primary name in event dictionary

For example:

• #{top_level}.#{segmentation}_#{event_name}
• count_all.projects_prometheus_active

Event Dictionary:

• product_owner: section, stage, group
• product_category: categories.yml
• implementation: snowplow js, snowplow ruby, redis hll, ordinary batch counter, etc.
• metric and event name
• description
• etc.

For example:

metric and event name	product owner	product category	implementation	...
count_all.projects_prometheus_active	ops.monitor	integrations	usage ping batch counting	...