Detect DSC Configuration file in repo use that as base for setup

[crutkas]

Suggested new feature or improvement

during cloning of a repository, we should detect the file and include this as part of the E2E setup process.

Scenario

Clone and your computer is setup automatically.

Additional details

No response

[denelon]

We should look at the ability to use the Git APIs to look for "*.dsc.yaml" files in the ".configuration" directory and use those during the setup flow to provide a better user experience. Then we can have the prompts all handled up front ahead of the clone and configure steps.

[joadoumie]

Issue #705 suggestion was for the following flow, which may be represented in this issue, but I'd like to make sure:

1. User downloads a .dsc.yaml file
2. User can right click on that file in File Explorer
3. User can navigate to Open With --> Dev Home
4. Dev Home is launched directly into the dsc config flow

If that flow is separate from the ask here, I may re-open it.

[shakersMSFT]

While this issue isn't using it as the base, we do have the work defined for detecting a configuration file found in a repo while cloning and allowing the user to run that file to complete their set up. #2211

[adrastogi]

@shakersMSFT (also tagging @dhoehna here for visibility)- for this functionality that detects a configuration file and gives the user the option to launch it via winget- has there been any consideration to having this driven via the configuration file flow in Dev Home itself?

What I was envisioning was that if the user clicks on the configuration file hyperlink on the summary info page, Dev Home would navigate over to the configuration flow (seeded with that configuration file). This feels like it would be a bit more of a streamlined experience since the user would remain in Dev Home throughout and can leverage the existing configuration file flow. Maybe there are other reasons that drove the current UX, so I wanted to ask first. Thanks!