Add fprintd-pam to a new critical-path-standard group

We had a situation with an fprintd update that broke su and
console logins:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-f997de7d0e
so clearly fprintd should be on the critical path. This is my
best guess as to how we should best do this (will discuss
details in the PR).

Signed-off-by: Adam Williamson <awilliam@redhat.com>

comps-f32.xml.in

@@ -686,6 +686,7 @@
       <packagereq type="mandatory">dbus-broker</packagereq>
       <packagereq type="mandatory">dnf</packagereq>
       <packagereq type="mandatory">dracut</packagereq>
+      <packagereq type="mandatory">fprintd-pam</packagereq>
       <packagereq type="mandatory">gcc-c++</packagereq>
       <packagereq type="mandatory">initial-setup</packagereq>
       <!-- 'kernel' is listed because we need to ensure that kernel

comps-f33.xml.in

@@ -658,6 +658,7 @@
       <packagereq type="mandatory">dbus-broker</packagereq>
       <packagereq type="mandatory">dnf</packagereq>
       <packagereq type="mandatory">dracut</packagereq>
+      <packagereq type="mandatory">fprintd-pam</packagereq>
       <packagereq type="mandatory">gcc-c++</packagereq>
       <packagereq type="mandatory">initial-setup</packagereq>
       <!-- 'kernel' is listed because we need to ensure that kernel

comps-f34.xml.in

@@ -754,6 +754,17 @@
       <packagereq type="default">notification-daemon</packagereq>
     </packagelist>
   </group>
+  <group>
+    <id>critical-path-standard</id>
+    <_name>Critical Path (standard)</_name>
+    <!-- not all deliverables include @standard, critical-path-base only includes stuff from @base -->
+    <_description>A set of packages that relate to Critical Path functionality and are in standard but not base</_description>
+    <default>false</default>
+    <uservisible>false</uservisible>
+    <packagelist>
+      <packagereq type="mandatory">fprintd-pam</packagereq>
+    </packagelist>
+  </group>
   <group>
     <id>critical-path-xfce</id>
     <_name>Critical Path (Xfce)</_name>