feat: track gen-ai use in Intercom COMPASS-7116

[paula-stacho]

https://jira.mongodb.org/browse/COMPASS-7116

Description

It seems feasible that the intercom track would be reused in the future, so I added it to utils - let me know if that's not the best place. The intercom setup is currently in the main compass package.
Also please consider if I missed any other place where NL is used 😅

The new tests for GenerativeAIInput are regression, I couldn't test the new behaviour because I couldn't put a spy on intercomTrack (not without moving it directly to the utils/index file or somewhere else completely).

Checklist

• New tests and/or benchmarks are included
• Documentation is changed or added
• I have signed the MongoDB Contributor License Agreement (https://www.mongodb.com/legal/contributor-agreement)

Motivation and Context

• Bugfix
• New feature
• Dependency update
• Misc

Open Questions

There are several logs associated with intercom setup. Do we want to log this event as well?

compass/packages/compass/src/app/intercom/intercom-script.ts

Line 55 in 0719486

log.info(

Types of changes

• Backport Needed
• Patch (non-breaking change which fixes an issue)
• Minor (non-breaking change which adds functionality)
• Major (fix or feature that would cause existing functionality to change)

[paula-stacho]

adding a wip label as I'm addressing some comments from @mcasimir

[paula-stacho]

@lerouxb added some changes after your review - a catch with a debug log, and an extra check ensuring we don't pollute external (Atlas) Intercom.

another suggestion from @mcasimir was to move the all the intercom code together. I will do this as a follow up in a separate PR

[lerouxb]

Just FYI: I don't think debug() would end up in a log file. If you're interested in seeing this in logs if it happens you would have to use log() on it.

[paula-stacho]

hmm, I thought it'd make sense to use the same level as when the intercom fails to load ->

compass/packages/compass/src/app/intercom/intercom-script.ts

Line 37 in 20a6ff8

.catch((e) => debug('queue error', e));

.
but tbh I'm not sure why that level was chosen in that instance either 🤔

[paula-stacho]

probably because it's not an user facing failure, so noone would look into the logs unless debugging anyway? or are there other cases where you'd imagine we'd need this in the logs?

[lerouxb]

The problem with debug() is that you can only see it if you have debug enabled and you're looking at the console or stdout. So it isn't something a user can spot in a log file and send it to us and we'd have to already know how to recreate the intercom failure in order to generate any debug output locally.

Which might be fine. Just thought I'd bring it up.