Microsoft.Winget.DSC/ApplyConfiguration - Nested Configurations

Description of the new feature / enhancement

There are times where it would be nice to create a partial configuration file for a project. For example - I could have a configuration file that only manages the configuration of VSCode, a configuration file that manages Git, a configuration file that manages my WinGet settings, etc.

In order to apply all of these, I would have to call each one separately. It would be useful to be able to be able to write a DSC file that can apply other DSC files.

This would also allow DSC files with many many configuration steps to be broken down into logical parts and re-assembled with a top-level DSC file that applies each of the parts.

Proposed technical implementation details

As a user, I would like to be able to have a DSC file that can apply other DSC files.

There are items that would need to be considered -

1. Preventing infinite loops (DSC files calling each other)
2. Conflicting states between files

No files, tests, or entry points are named in the issue. Start by locating the Microsoft.Winget.DSC configuration-application handling, then determine how nested files, cycles, and conflicting states should be represented. Done means a top-level DSC file can apply other DSC files safely with defined behavior for loops and conflicts.