[Search:SearchApplications:Docs Explorer page]Issues with tour popover near Configuration button

[L1nBra]

Description
Tour popover appears near Configuration button and covers buttons behind it. It is reachable with keyboard, but user has to navigate to Notebooks button first and then after it tour popover is reached.
Navigation has to be in logical sequence as well and elements should not cover over elements or it would be better for user to be able to dismiss tour popover before navigating to covered (due to popover) elements.

Preconditions
Stateful Search Applications -> Docs Explorer page is opened for the first time (or without tour dismissed).
Search application is added.
Use Screen Reader (NVDA).

Steps to reproduce

1.Using only keyboard Navigate to tour popover Close tour button by pressing Tab key.
2.Observe the page.
3.Observe screen reader.
4.Press Esc key.

Gif showing issue

NVDA Speech Viewer + UI elements

Actual Result

• After Search field user visually doesn't see focus nor the elements (buttons) which are behind the popover: View API call, Search.
  Focus is on tour popover close button only after Notebooks button. Tour popover is announced as dialog, but when user presses Esc key it is not closed.

Expected Result

• After configuration button, focus goes to tour popover Close tour button when popover is present. That way after closing popover if user continues navigation, he/she will be able to clearly see View API call, Search buttons.
  If element should really be announced as dialog, then Esc key should close the popover.

Meta Issue

Kibana Version: 8.17.0-SNAPSHOT

OS: Windows 11 Pro

Browser: Chrome Version 130.0.6723.70 (Official Build) (64-bit)

Screen reader: NVDA

WCAG or Vendor Guidance (optional)

• Understanding SC 1.3.1: Info and Relationships (Level A)(https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.html)
• Understanding SC 4.1.2: Name, Role, Value (Level A)(https://www.w3.org/WAI/WCAG22/Understanding/name-role-value.html)
• Understanding SC 2.4.3: Focus Order (Level A)(https://www.w3.org/WAI/WCAG22/Understanding/focus-order.html)
• Understanding SC 2.4.11: Focus Not Obscured (Minimum) (Level AA)(https://www.w3.org/WAI/WCAG22/Understanding/focus-not-obscured-minimum.html)

Related to: https://github.com/elastic/search-team/issues/8256

[elasticmachine]

Pinging @elastic/kibana-accessibility (Project:Accessibility)