Enable Policheck 🌎 per Compliance to Scan for Offensive Terms (#1811)

* Enable Policheck

* Remove the old pipeline

We probably should have done this post 1ES Migration

* azdo is being buggy and not letting me move from 1 to another
so undo this and do it in another pr
Revert "Remove the old pipeline"

This reverts commit 3c4cc97.

* azdo is buggy no more
Revert "azdo is being buggy and not letting me move from 1 to another"

This reverts commit 012133f.

1es-azure-pipeline.yml

@@ -54,6 +54,9 @@ extends:
         name: NetCore1ESPool-Internal
         image: 1es-windows-2022
         os: windows
+      policheck:
+        enabled: true
+        exclusionsFile: $(System.DefaultWorkingDirectory)\PoliCheckExclusions.xml
     stages:
     - stage: Internal
       jobs:

PoliCheckExclusions.xml

@@ -0,0 +1,10 @@
+<PoliCheckExclusions>
+    <!--Each of these exclusions is a folder name -if \[name]\exists in the file path, it will be skipped -->
+    <Exclusion Type="FolderPathFull">NODE_MODULES|.STORE</Exclusion>
+    <!--Each of these exclusions is a folder name -if any folder or file starts with "\[name]", it will be skipped -->
+    <!-- <Exclusion Type="FolderPathStart">ABC|XYZ</Exclusion>-->
+    <!--Each of these file types will be completely skipped for the entire scan -->
+    <!-- <Exclusion Type="FileType">.ABC|.XYZ</Exclusion>-->
+    <!--The specified file names will be skipped during the scan regardless which folder they are in -->
+    <!-- <Exclusion Type="FileName">ABC.TXT|XYZ.CS</Exclusion>-->
+</PoliCheckExclusions>