Add Usage data tracking using Redis HLL for UI events

What does this MR do?

Add UsageData#increment_unique_values API

• Add usage_data_api feature, enabled by default in order to be able to stop if we see scaling issues

• Users should be authenticated in order to be able to call this method

• Documentation is only under Telemetry guide

• Open a follow up issue to see how to handle unauthenticated users #246823 (closed)

• Allow known_events only this is already done, we could count only on metrics defined in known_events.yml

• Allow to send any values(values will be in responsibility of the API users) with the mention that we do a check

  • for the string value size, allow strings of max 36 size(choosing this as it is a use case at the moment)
  • and size of the array that we allow to receive, maybe test with different array sized(I would start with 10 elements) There is no real use case at this moment

Screenshots

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team

cc @jeromezng

Related #235459 (closed)