`winget configure` accepts a directory

Relevant area(s)

WinGet CLI

Description of the new feature / enhancement

The configuration exported by winget configure export --all is already very large. As a user, I may want to split the configurations into multiple files for maintainability. I also could have separate configurations for configuring multiple projects. I'd like a way to be able to specify a directory path where winget configure looks for all configuration files in the directory and executes each of them. This could be more than just syntactic sugar wherein if multiple steps are repeated in different configuration files, then WinGet should be able to detect those and skip redundant execution. Before execution, WinGet may consolidate all files into one logical configuration mapping out any dependencies across multiple configurations.

Proposed technical implementation details

No response

Start at the WinGet CLI's configure command and trace how it accepts and loads a configuration file. Define expected directory discovery, ordering, dependency handling, and duplicate-step behavior before locating relevant tests. Done means directory input is supported with clear behavior and coverage for multiple files and repeated steps.