Gitlab::Tracking data point for VisualReviewDiscussion API

Merged drew cimino requested to merge visual-review-api-tracking into master

What does this MR do?

This adds a tracking call to the helper method used to create anonymous merge request discussions. It felt a little hacky to write the call to Gitlab::Tracking directly into the Grape endpoint code, so I went one level further in and it seems like a tidy enough place.

I grabbed the code directly out of the engineering handbook page, but there's no accompanying tests or verification that this is good and works. There's also some conceptual checking to do about what the data point needs to have with the data team, product, or telemetry. Once I get some answers around that, we can also update the engineering handbook.

This closes #11944 (closed), which has been enabled by #29067 (closed) / !18710 (merged)

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

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
Edited by drew cimino