Split dotnet configs

.NET 8/9/10 will all be supported soon (until the earlier versions go EOL
in 2026), where ELN will soon be able to move to 10 and drop 8 and 9.  Like
with Java, this drifting overlap between RHEL and ELN is best handled with
separate configs for each version and just toggling labels as needed.

.NET STS releases (e.g. 9) now have 24 months of upstream support:

https://devblogs.microsoft.com/dotnet/dotnet-sts-releases-supported-for-24-months/

Author: yselkowitz

configs/rhel-pt-dotnet--dotnet10.yaml

@@ -0,0 +1,13 @@
+document: feedback-pipeline-workload
+version: 1
+data:
+  name: .NET 10
+  description: .NET 10 SDK, tools and runtime
+  maintainer: rhel-pt-dotnet
+  packages:
+    # EOL in Nov, 2028
+    - dotnet-sdk-10.0
+    - dotnet-runtime-10.0
+    - aspnetcore-runtime-10.0
+  labels:
+    - c10s

configs/rhel-pt-dotnet--dotnet.yaml renamed to configs/rhel-pt-dotnet--dotnet8.yaml

@@ -1,18 +1,14 @@
 document: feedback-pipeline-workload
 version: 1
 data:
-  name: .NET
-  description: .NET SDK, tools and runtime
+  name: .NET 8
+  description: .NET 8 SDK, tools and runtime
   maintainer: rhel-pt-dotnet
   packages:
     # EOL in Nov, 2026
     - dotnet-sdk-8.0
     - dotnet-runtime-8.0
     - aspnetcore-runtime-8.0
-    # EOL in May, 2026
-    - dotnet-sdk-9.0
-    - dotnet-runtime-9.0
-    - aspnetcore-runtime-9.0
   labels:
     - eln
     - c10s

configs/rhel-pt-dotnet--dotnet9.yaml

@@ -0,0 +1,14 @@
+document: feedback-pipeline-workload
+version: 1
+data:
+  name: .NET 9
+  description: .NET 9 SDK, tools and runtime
+  maintainer: rhel-pt-dotnet
+  packages:
+    # EOL in Nov, 2026
+    - dotnet-sdk-9.0
+    - dotnet-runtime-9.0
+    - aspnetcore-runtime-9.0
+  labels:
+    - eln
+    - c10s