[build] Revert BinSkim analyzeTargetGlob customization (#10964)

Revert the `analyzeTargetGlob` customization added in PRs #10940, #10953, and #10961.

The custom glob patterns caused more problems than they solved:

- `+|bin\Build*\**` — Guardian can't parse `+|` prefix (#10953)
- `bin\Build*\**` — breaks the 'Convert NuGet to MSI' job which has no `bin\Build*\` directory (#10961)
- `bin\Build*\**;bin\msi-nupkgs\**` — Guardian can't parse semicolons, breaks every job

Remove `analyzeTargetGlob` entirely and keep only `scanOutputDirectoryOnly: true`, which is the default configuration that worked before #10940.

Author: jonathanpeppers

build-tools/automation/azure-pipelines.yaml

@@ -60,12 +60,6 @@ extends:
         enableAllTools: false
       binskim:
         scanOutputDirectoryOnly: true
-        # Scan build output and MSI conversion output, but not test assemblies
-        # under bin/Test* which produce BA2021 false positives.
-        # Both patterns are needed because the 1ES template applies sdl config
-        # globally: build/test jobs produce bin\Build*\ output, while the
-        # "Convert NuGet to MSI" job only produces bin\msi-nupkgs\ output.
-        analyzeTargetGlob: bin\Build*\**;bin\msi-nupkgs\**
       codeql:
         compiled:
           enabled: false