Feat/add telemetry for toasts 166459 2

[vadimkibana]

Original PR: #166466

• This PR changes the original by only removing the title field from telemetry.

Closes #166466

---

Original:

Summary

Address #166459

This PR scaffolds telemetry into the notification service, to enable reporting when deduped toasts are dismissed. When a deduped toast is dismissed; the message recurrence count and the toast message would be emitted.

Telemetry Event Definition;

{
 eventType: "global_toast_list_toast_dismissed",
 schema: {
   "toast_deduplication_count": {
      type: "long",
      _meta: {
        description: "toast message text"
      }
   },
  "toast_message": {
      type: "keyword",
      _meta: {
        description: "recurrence count for particular toast message"
      }
   },
 "toast_message_type": {
      type: "keyword",
      _meta: {
        description: "toast message type, accepted values are warning, danger, primary"
      }
   }
 }
}

Testing;

• Ensure you have an existing dashboard, if you don't installing any sample data would bootstrap a dashboard automatically
• Search for visualize library from the global search bar, and navigate to visualize library.
• Attempt to create a visualization, select the TSVB visualization type. At this step there typically wouldn't be an error
• We can simulate an error, by open Dev tools and blocking the URL /internal/metrics/vis/data like so
  on doing this, we then attempt refreshing the query, we would then be presented with an error toast, similar to the screenshot below;
  
  click the refresh query button as much as you like to increase it's recurrence count.
• From here on we verify that; clicking the dismiss button sends a telemetry event, also not interacting with the toast and it's display lifetime elapsing with the toast clearing itself, the telemetry gets sent still. In either case there should be a request calling the resource kibana_browser with a payload containing the telemetry event definition above.

Checklist

• Unit or functional tests were updated or added to match the most common scenarios

[elasticmachine]

Pinging @elastic/appex-sharedux (Team:SharedUX)

[vadimkibana]

@elasticmachine merge upstream

[pgayvallet]

LGTM

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: bf875b8

Failed CI Steps

• FTR Configs #27
• FTR Configs #30
• FTR Configs #33
• FTR Configs #60

Test Failures

• [job] [logs] FTR Configs #33 / discover/group1 shared links shared links with state in sessionStorage sharing hashed url shouldn't crash the app
• [job] [logs] FTR Configs #60 / serverless common UI Index Management Create enrich policy "before all" hook for "shows create enrich policies page and docs link"
• [job] [logs] FTR Configs #27 / serverless search UI empty pages "before all" hook for "should show search specific empty page in discover"
• [job] [logs] FTR Configs #30 / serverless security UI Create Case "before each" hook for "creates a case"

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
core	483	486	+3

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
core	366.4KB	367.4KB	+936.0B

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream