Run as administrator profiles do not run until terminal is ran as administrator.

Nobody has claimed this yet.

### Windows Terminal version

1.14.1963.0

### Windows build number

10.0.22000.832

### Other Software

_No response_

### Steps to reproduce

1. Log in to windows as a standard user without administrative permissions
2. Create a new profile and configure it to run as administrator.
3. Save the settings and try to run the profile

### Expected Behavior

When the profile is ran under the standard non-admin account, the system should prompt the user for administrator credentials. Once the credentials are entered, the profile should run in a new windows with administrator permissions.

### Actual Behavior

After entering credentials to the user account control prompt, the profile does not run. Instead it's execution (and appearance of its windows) is delayed until a new instance of terminal is ran as administrator.

This issue does not affect administrator accounts, it only occurs for accounts that are not in the administrators group.

Reproduce the issue using a standard Windows user, a profile configured to run as administrator, and the listed Windows Terminal and Windows build versions. Trace the profile launch and credential-prompt behavior; done means the profile opens with administrator permissions immediately after valid credentials are entered, without requiring another elevated Terminal instance.

Written by the indexing model from the issue text.