Instrument tracking for JWT token usage using Service Ping

Proposal

Since we are releasing a new version of the JWT, its worth implementing a new way to collect the data from our users to track its adoption.

Let's measure the unique number of unique users that are using id_token: in their pipeline, similar to the way we track SECRETS:

Additionally, this issue should include the Sisense implementation that enables us to visualize the data.

Implementation

backend	MR
CI JWT token usage instrumentation with Service Ping	!109686 (merged)

The above MR implements new instrumentation metric for Service Ping payload with key paths:

redis_hll_counters.ci_secrets_management.i_ci_secrets_management_id_tokens_build_created_monthly

redis_hll_counters.ci_secrets_management.i_ci_secrets_management_id_tokens_build_created_weekly

Note that the count of users/installations broken down by tiers is available for Self-Managed instances only. This is a limitation of Service Ping as noted here. Data for SaaS instances to be implemented with Snowplow in this issue.

Sisense Implementation

Charts created for tracking JWT Token usage in Self-Managed instances. See Secrets Management Dashboard