Dev Setup on a fresh Windows install fails.

### Describe the bug

Attempting to follow the developer setup as described in ```docs\GettingStarted.md``` leads to failure reports in the one-time 'pre-build' setup steps, further leading to ```ebfp-for-windows``` build failure for the ```msbuild``` command-line build.

This issue is seen with the command-line build _only_. VS2022 GUI build completes successfully.

### OS information

SKU: Windows 11 Pro
Version: 22H2
Build: 22623.1028 (Insider ‘Beta’ Channel)

### Steps taken to reproduce bug

1. Begin with a clean install of Windows 11 Pro, updated to the insider version specified in the 'OS Information' section above. Ensure that this install _does_ _not_ have any prior installation of Visual Studio and/or windows SDK, WDK components.
3. Follow the steps outlined in the ```ebpf-for-windows\docs\GettingStarted.md``` doc to install the various pre-requisite components in the suggested sequence.
4. Clone the ```ebpf-for-windows``` repo and ```cd``` to the repo root.
5. Follow the one-time pre-build steps outlined in the 'How to clone and build the project using Visual Studio->Prepare for first build' section.

### Expected behavior

The one-time pre-build steps should complete without any errors and a subsequent ```msbuild``` command line build attempt should succeed without any errors.

### Actual outcome

The command ```nuget restore ebpf-for-windows.sln``` from the one-time 'pre-build' steps reports multiple instances of this error:

```error MSB4019: The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.Cpp.Default.props" was not found. ```

This leads to a subsequent build failure for the ```msbuild``` command line build.

A full log (```ebpf_vs2022_fresh_install.txt```) of the required one-time 'pre-build' steps along with a subsequent ```msbuild``` command-line build attempt is attached.

[ebpf_vs2022_fresh_install.txt](https://github.com/microsoft/ebpf-for-windows/files/10223229/ebpf_vs2022_fresh_install.txt)

### Additional details

Not sure if this is germane to the issue at hand but in my attempt, the WDK installer also complained about _not_ detecting the 'Desktop C++ Development' workload in the available instance of Visual Studio, in spite of its verified presence.

This warning did not seem to have any effect on the subsequent install of the WDK components themselves or the post-WDK-install VS integration either.

Start with docs\GettingStarted.md and reproduce the one-time setup from a clean Windows 11 installation. Run nuget restore ebpf-for-windows.sln and the subsequent msbuild command, then compare the failures with ebpf_vs2022_fresh_install.txt. Done means the pre-build steps and command-line build complete without errors.

Written by the indexing model from the issue text.