[ez][HUD] Put XPU workflow into it's own group (#7052)

Reason:
Currently the xpu workflow is being put into the linux group, but the
xpu workflow is only run periodically on main and is frequently broken,
which makes the linux column on hud confusing since it will look like
it's failing but it's just xpu

XPU workflow isn't usually run on PRs usually so it doesn't affect many
devs, so we've let the XPU team handle its failures at their own pace

At what point do we start grouping by workflow instead of platform and
other things in the job name?

Author: clee2000

torchci/lib/JobClassifierUtil.ts

@@ -28,6 +28,7 @@ const GROUP_PARALLEL = "Parallel";
 const GROUP_DOCS = "Docs";
 const GROUP_LIBTORCH = "Libtorch";
 const GROUP_OTHER_VIABLE_STRICT_BLOCKING = "Other viable/strict blocking";
+const GROUP_XPU = "XPU";
 const GROUP_OTHER = "other";
 
 // Jobs will be grouped with the first regex they match in this list
@@ -48,6 +49,10 @@ export const groups = [
     regex: /unstable/,
     name: GROUP_UNSTABLE,
   },
+  {
+    regex: /^xpu/,
+    name: GROUP_XPU,
+  },
   {
     regex: /inductor-periodic/,
     name: GROUP_INDUCTOR_PERIODIC,
@@ -156,6 +161,7 @@ const HUD_GROUP_SORTING = [
   GROUP_IOS,
   GROUP_MAC,
   GROUP_ROCM,
+  GROUP_XPU,
   GROUP_XLA,
   GROUP_OTHER_VIABLE_STRICT_BLOCKING, // placed after the last group that tends to have viable/strict blocking jobs
   GROUP_PARALLEL,