[Security:Assets:Fleet:Add Integration page]Incorrect navigation

[L1nBra]

Description
Navigation has to be in sequence and in logical order. After closing, canceling dialogs/flyouts, activating elements - navigation should go to the element which activation opened dialog, to the first element which appeared after button activation. Otherwise user will need to navigate longer in order to come back to the element which opens dialog, to reach new elements.

Preconditions
Security -> Assets -> Fleet -> Add Integration page is opened.

Steps to reproduce

1.Using only keyboard navigate to Add condition button by pressing Tab key.
2.Press Enter.
3.Add any condition (f.e.: Container image tag).
4.Press Tab key few times.
5.Observe page.

Screen recording
https://github.com/user-attachments/assets/18f26049-2f35-495e-acc5-6e1907ae9c8f

Actual Result

• Navigation stays on Add condition button and moves to the next element.

Expected Result

• Navigation goes to newly appeared field Container image tag.

Notes:
Similar behavior when:
-Adding selector. Navigation goes to the next element instead of newly added selector first element.

-Adding response. Navigation goes to the next element instead of newly added response first element.

-Excluding selectors. Navigation goes to the next element instead of newly appeared Exclude selectors fields.

-closing Kibana API Request flyout. Navigation goes to Skip to main content instead of Preview API Request button.

Meta Issue

Kibana Version: 8.17.0-SNAPSHOT

OS: Windows 11 Pro

Browser: Chrome Version 131.0.6778.140 (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/kibana-team/issues/1280

[elasticmachine]

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

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)