[7.10][Telemetry] Update data collection panel to show example security event.

[pjhampton]

Summary

Resolves #68942
Related to #77200
Related to elastic/protections-team#172 (Data Engineering)

This PR adds a fly-out with an example of a security event collected from Elastic Endpoint when enabled.

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Unit or functional tests were updated or added to match the most common scenarios
• This was checked for keyboard-only and screenreader accessibility
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser
• This was checked for cross-browser compatibility

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[pjhampton]

@elasticmachine merge upstream

[pjhampton]

@TinaHeiligers RE

The usage data is the only section that doesn't have the title there. So for consistency, it would be better to also list there.

I spent an hour looking into this. It is because the Telemetry Management Section registers itself as a footer to the Advanced Settings plugin:

kibana/src/plugins/telemetry_management_section/public/plugin.tsx

Lines 41 to 51 in 80c004c

	export class TelemetryManagementSectionPlugin implements Plugin {
	public setup(
	core: CoreSetup,
	{ advancedSettings, telemetry: { telemetryService } }: TelemetryManagementSectionPluginDepsSetup
	) {
	advancedSettings.component.register(
	advancedSettings.component.componentType.PAGE_FOOTER_COMPONENT,
	telemetryManagementSectionWrapper(telemetryService),
	true
	);
	}

(See L47)

I had my findings confirmed by a Kibana Arch team member. They described the change as a non-negligible amount of coding. Because of not wanting to hold this change up it can be addressed in another PR - either by me or you. Regardless, this was a great find by the design team!

[kibanamachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request
• Commit: e05e1f9
• Pipeline Steps (look for red circles / failed steps)
• Interpreting CI Failures

Failed CI Steps

• Jest Unit Tests

---

Test Failures

Jest Tests.src/plugins/telemetry_management_section/public/components.OptInDetailsComponent security flyout renders as expected

Link to Jenkins

Standard Out

Failed Tests Reporter:
  - Test has not failed recently on tracked branches

Stack Trace

Error: expect(received).toMatchSnapshot()

Snapshot name: `OptInDetailsComponent security flyout renders as expected 1`

- Snapshot  - 2
+ Received  + 2

@@ -77,16 +77,16 @@
      "agent": {
        "id": "b2e88aea-2671-402a-828a-957526bac315"
      }
    },
    "file": {
-     "path": "C:\\Users\\User\\Downloads\\mimikatz_trunk\\x64\\mimikatz.exe",
+     "path": "C:\\Windows\\Temp\\mimikatz.exe",
      "size": 1263880,
      "created": "2020-05-19T07:50:06.0Z",
      "accessed": "2020-09-22T14:29:19.93531400Z",
      "mtime": "2020-09-22T14:29:03.6040000Z",
-     "directory": "C:\\Users\\User\\Downloads\\mimikatz_trunk\\x64",
+     "directory": "C:\\Windows\\Temp",
      "hash": {
        "sha1": "c9fb7f8a4c6b7b12b493a99a8dc6901d17867388",
        "sha256": "cb1553a3c88817e4cc774a5a93f9158f6785bd3815447d04b6c3f4c2c4b21ed7",
        "md5": "465d5d850f54d9cde767bda90743df30"
      },
    at Object.it (/dev/shm/workspace/parallel/6/kibana/src/plugins/telemetry_management_section/public/components/opt_in_security_example_flyout.test.tsx:25:81)
    at Object.asyncJestTest (/dev/shm/workspace/kibana/node_modules/jest-jasmine2/build/jasmineAsyncInstall.js:100:37)
    at resolve (/dev/shm/workspace/kibana/node_modules/jest-jasmine2/build/queueRunner.js:45:12)
    at new Promise (<anonymous>)
    at mapper (/dev/shm/workspace/kibana/node_modules/jest-jasmine2/build/queueRunner.js:28:19)
    at promise.then (/dev/shm/workspace/kibana/node_modules/jest-jasmine2/build/queueRunner.js:75:41)
    at process._tickCallback (internal/process/next_tick.js:68:7)

---

Metrics [docs]

‼️ ERROR: no builds found for mergeBase sha [012b6fe]

History

• 💔 Build #78220 failed e05e1f9
• 💔 Build #78186 failed 0c6e08d
• 💔 Build #78182 failed 3ba7b59
• 💚 Build #77755 succeeded f8ee688

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

[afharo]

I think this branch was originally created from 7.x as a base and it's messing up quite a lot when now trying to merge it into master. @pjhampton can you rebase your branch to master instead (or maybe it'll be easier to create a new branch from master and apply the changes again)

[pjhampton]

Yeah, agreed @afharo. This branch is toast. I will re-open a fresh PR 👍