Require only dnf5 in ELN

While some packages still need to be ported from libdnf or python3-dnf and
will remain in ELN in the meantime, the goal is to fully transition to dnf5
for RHEL 11 and therefore dnf-4 should not be listed as required.

dnf5 also provides/obsoletes microdnf, so the minimal workload is obsolete.

Author: yselkowitz

configs/rhel-sst-cs-software-management--package-manager-devel.yaml

@@ -12,5 +12,4 @@ data:
     - python3-rpm
     - rpm-devel
   labels:
-    - eln
     - c10s

configs/rhel-sst-cs-software-management--package-manager-dnf5-devel.yaml

@@ -0,0 +1,15 @@
+document: feedback-pipeline-workload
+version: 1
+data:
+  name: Package Manager - development packages
+  description: Supported development packages
+  maintainer: rhel-sst-cs-software-management
+  packages:
+    - dnf5-devel
+    - libdnf5-devel
+    - libdnf5-cli-devel
+    - popt-devel
+    - python3-rpm
+    - rpm-devel
+  labels:
+    - eln

configs/rhel-sst-cs-software-management--package-manager-minimal.yaml

@@ -8,5 +8,4 @@ data:
     - microdnf
     - rpm
   labels:
-    - eln
     - c10s