[Keyboard Navigation - Logic apps - Search]: Keyboard focus doesn't land on first interactive control on activating "HTTPS" button.

### Describe the issue

User Experience:

Users with motor or visual disabilities who depend on the keyboard to navigate the application will be misguided and face difficulty in accessing the elements due to which extra tab navigation is required to reach desired control.

Note: User credentials should NOT be included in the bug.

Pre-requisites:

- Make sure dependencies such as Azure Logic Apps (Standard), Azure Functions, C# are installed.
- Navigate to Azure control present on the right side and select it.
- Navigate to LogicApp icon present under workspace section, click on tat and select 'Create New Project'.
- Navigate select stateful workflow, then enter the name of the workflow.
- Once the workflow has been created then enter the name of the created workflow in edit field present on the top and press Enter.
- Navigate to 'Open in current window' and select it.
- A dialog will appear, select 'Yes', now the workflow will open in new window.

Repro Steps:

- Open Visual Studio app.
- Navigate to any workflow and right click on it, then select 'open designer'.
- Navigate all the controls of the designer screen.
- Navigate to send message box and select it, a new blade appears on right side.
- Navigate all the controls of 'Parameters' tab.
- Observe if keyboard focus doesn't land on first interactive control on activating "HTTPS" button.

Actual Result:

Keyboard focus doesn't land on first interactive control on activating "HTTPS" button instead focus moves to all design section controls then lands on "Collapse" button of new dialog.

Expected result:

Keyboard focus should land on first interactive control i.e "Collapse" button of new dialog on activating "HTTPS" button instead of focus moving all design section controls.

### Are you using new designer or old designer

New Designer (With action panels)

### Screenshots or Videos

*No response*

### Browser

Chrome, Edge, Safari

### Additional context

*No response*