Remove BuildTools as it is part of VS

[mattleibow]

Description of Change

Remove the BuildTools from the manifest because this is not a runtime package and also it already exists in VS.

Since it is not a runtime package, we can't really include it in the way we need:

VALIDATEMANIFEST : warning : PackageDependenciesAreSatisfiedWarnings failed : Dependencies for chip='', language='' : The dependent package of 'maui.windows,version=#NUM#.#NUM#.#NUM#.#NUM#' cannot be found: Microsoft.Windows.SDK.BuildTools.#NUM#.#NUM#.#NUM#.#NUM#,version=#NUM#.#NUM#.#NUM#.#NUM#. : [manifest=VisualStudio/#NUM#.#NUM#.#NUM#+#NUM#.#NUM#.main]

Also removing the WASDK from the inserting because of missing symbols.

[pjcollins]

Given the sign check issues we're also seeing, I think we will want to remove both this and the Microsoft.WindowsAppSDK package from the workload for now.

[mattleibow]

The failing files are:

• bin\10.0.22000.0\x64\deployutil.exe
• bin\10.0.22000.0\arm64\deployutil.exe
• bin\10.0.22000.0\arm\deployutil.exe
• bin\10.0.22000.0\x86\deployutil.exe

Is it possible to ignore this folder as it is a tool used at build time?

[pjcollins]

We could potentially get an exception for deployutil.exe in Microsoft.Windows.SDK.BuildTools, but there are also 220 unsigned files in the Microsoft.WindowsAppSDK package that would also need to be addressed. I think the signing issues would be a harder sell, and we'll probably need to engage with the team producing these packages to figure out next steps.