[Stateful:Indices:Pipelines page] Incorrect navigation when completing Add an inference pipeline steps in sequence

[L1nBra]

Description
Even though for Flyouts webpage elements are accessible, there should be a consistency with navigation. When moving from one step to another after activating Continue button, navigation should continue directly on the current step. It could move to the first element on the webpage when user presses Tab key on Continue button (not activates it).
Otherwise, users using keyboard only, has to go through more elements in order to complete the steps which would take longer for them.

Preconditions
Stateful Indices -> Pipelines page is opened.

Steps to reproduce

1.Navigate to Add an inference pipeline button while using only keyboard by pressing Tab key.
2.Press Enter.
3.Complete step 1 (select any trained ML model and enter any name if not filled automatically).
4.Navigate to Continue button while pressing Tab key.
5.Press Enter.
6.Complete step 2 (enter anything, f.e.: test in Source text field and Add it).
7.Navigate to Continue button while pressing Tab key.
8.Press Enter.
9.Press Tab few times.
10.Observe the page.

Gif showing issue

UI elements

Actual Result

• When step 3 is present on the screen, navigation starts from the first element on the page.
  Same behavior with step 4.

Expected Result

• Navigation starts from the Add an inference pipeline Flyout.

Notes:
When pressing Enter on Add an inference pipeline button and then navigating with Tab - navigation starts from the opened Flyout. After completing step 1, navigating to Cancel button and pressing Enter - step 2 opens. When pressing Tab key, navigation also starts from the Flyout.
If user navigates back to step 1, then goes to Continue button - navigation from step 2 starts from the first element on the webpage, not directly on the Flyout.

Meta Issue

Kibana Version: 8.16.0-SNAPSHOT

OS: Windows 11 Pro

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

WCAG or Vendor Guidance (optional)

• Understanding SC 2.4.3: Focus Order (Level A)(https://www.w3.org/WAI/WCAG22/Understanding/focus-order.html)

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

[elasticmachine]

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