[Discover][Profiles] Add profileId for document profiles in telemetry context for relevant events

[iblancof]

Summary

Background
With the introduction of profiles in Discover, the discoverProfiles attribute was added to the telemetry context to include the profileId for active Data Source Profiles.

While working on the Document Profile implementation, I noticed that the profileId is not included in the discoverProfiles attribute for document profiles in the event context.

Why?
As explained by @jughosta, it wasn't implemented because multiple document profiles can be resolved on the same page depending on the data in the rows. Adding them to the discoverProfiles attribute on load (as is done for data source profiles) wouldn't clarify which profile was actually in action at the time of the event.

Goal
The goal of this issue is to add the profileId for document profiles when relevant. This may involve manually adding the event context in specific cases when using the ebtManager.

For example, when calling onAddFilter from the flyout, we could pass the context for that specific event optionally, making sure it doesn't unintentionally carry over to other events.

[elasticmachine]

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)