Summary

DO NOT MERGE - POC only

This draft PR explores integration and capabilities of new [Epic] Flyout System within Discover - both for our internal use and as an extension point for contextual profiles ([OneDiscover][Extension] Full Fly-out Extension Point for Document Viewer in Discover)

With the new flyout system, we can enhance our background searches flyout and let user explore a single session within a child flyout:

As per extension point, having minimal changes in Unified Doc Viewer (setting prop session to start) and swapping traces waterfall fullscreen component to a flyout with session='inherit' we're able to enhance traces exploration:

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
• Flaky Test Runner was used on any tests changed
• The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
• Review the backport guidelines and apply applicable backport:* labels.

Identify risks

Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.

• See some risk examples
• ...