This helps the InTel team understand which queryStats entries were queries originating from the InTel control plane.

An alternative way to distinguish queries coming from the user and Atlas control plane is to utilize the appName field, which has a much higher cardinality and has more variance than the `username` field, so it's less feasible than including the `username` field, which is a required parameter for any connection.

The root problem here is that InTel team wants to add a "filter out internal operations" UI for query shape insights, and needs the proper metadata to do so.

For context - we've had this discussion before. there are 3 types of queries:
(1) internal (server originated)
(2) internal (from the control plane)
(3) from a user

the idea is that this UI toggle would filter out 1 & 2.