Support mixed elevation requirements in configuration files

[denelon]

Description of the new feature / enhancement

I want to be able to use a single WinGet Configuration file to configure my system. If for example, I have two packages with opposing elevation requirements, I want WinGet to be able to do the right thing.

The configuration file will need to be decorated appropriately so DSC Resources requiring elevation and those prohibiting elevation can be clearly identified.

WinGet should be able to run only the resources requiring elevation with elevation and all others without elevation.

Proposed technical implementation details

No response

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• Handle opposing elevation requirements for packages with dependencies. (#3675), similarity score: 0.79

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[whindsaks]

It should be smart enough to detect the elevation requirement right away so it can UAC prompt, not after first having installed x number of per-user apps.

[denelon]

This work was completed for the COM API leveraged by Dev Home, but we still need to do the work for this to function properly in the CLI and the PowerShell cmdlets.

[denelon]

• Improve configuration self elevation flow #4844