(docs) Add a feature page regarding autoUninstaller

This adds a new page about the Automatic Uninstaller to consolidate
information about it into a single page and give some more details about
how it works.

Author: corbob

src/content/docs/en-us/choco/features/auto-uninstaller.mdx

@@ -0,0 +1,23 @@
+---
+order: 30
+xref: auto-uninstaller
+title: Automatic Uninstaller
+description: Chocolatey's Automatic Uninstaller removes software so you don't have to.
+---
+import Callout from '@choco-astro/components/Callout.astro';
+import Iframe from '@choco-astro/components/Iframe.astro';
+import Xref from '@components/Xref.astro';
+
+<Callout type="warning">
+    Chocolatey CLI Automatic Uninstaller is a powerful feature that can result in unexpected results. If you install other software while a package is being installed, Chocolatey CLI will detect these additional installations and will automatically uninstall them for you, when you uninstall the package.
+</Callout>
+
+![Auto Uninstaller](/images/features/features_auto_uninstall.png)
+
+The Automatic Uninstaller feature in Chocolatey CLI looks at the software installed on the computer, before a package is installed, and after a package is installed. Knowing what software has been installed on the computer by a package, allows Chocolatey CLI to automatically uninstall that software when uninstalling the package, without any additional effort.
+
+### How do I skip the Automatic Uninstaller?
+
+If you are trying to uninstall a package, but the Automatic Uninstall feature is uninstalling software you don't want to be uninstalled, then it can be skipped by using the `--skip-autouninstaller` option on the command line. You can <Xref title="disable the feature" value="configuration" anchor="automatic-uninstaller" /> by setting the `autoUninstaller` feature to `false`
+
+If you are <Xref title="creating a package" value="package-creation-guide" />, and want to use the `chocolateyUninstall.ps1` to uninstall software without using the Automatic Uninstaller, include an empty file with the name `.skipAutoUninstall`, inside the package. This will stop the Automatic Uninstaller for that specific package. If a `.skipAutoUninstall` file is being included, make sure that it is included in the `files` element of the `.nuspec`, either explicitly via a `file` element, or by placing the file inside a folder that is included inside the package (like the `tools` directory).

src/content/docs/en-us/faqs.mdx

@@ -339,9 +339,7 @@ If this is hard coded for a package that runs an installer, it may display an in
 
 ### How do I skip the Automatic Uninstaller?
 
-If you are trying to uninstall a package, but Automatic Uninstall is uninstalling software you don't want uninstalled, or otherwise misbehaving, then it can be skipped by using the `--skip-autouninstaller` switch, or disabling it by setting the `autoUninstaller` feature to `false`.
-
-If you are creating a package, and want or need to use the `chocolateyUninstall.ps1` while not running the Automatic Uninstaller, then include a `.skipAutoUninstall` file inside the package. If a file with that name is found, then during uninstall the Automatic Uninstaller will not be run. If a `.skipAutoUninstall` file is being included, make sure that it is included in the `files` element of the `.nuspec`, either explicitly via a `file` element, or by placing the file inside a folder that is included inside the package (like the `tools` directory).
+Please see the <Xref title="feature documentation" value="auto-uninstaller" />.
 
 ## Videos / Reference
 
@@ -492,4 +490,4 @@ A typical way of stating the difference is "Developers use NuGet to get 3rd part
 ### How is/will Chocolatey be different than apt?
 
  * Chocolatey does not support the idea of source packages, which are packages that must be built to be used. For someone interested in that, check out https://github.com/Microsoft/vcpkg.
- * Library packages are not completely off the plate, but mostly. How would you link the library up to the application/tool?
+ * Library packages are not completely off the plate, but mostly. How would you link the library up to the application/tool?