Add stable queue branches

[sashalevin]

These branches are automatically generated whenever we modify the stable queue. Getting these tested will allow us to stop abusing the -rc branches just to get bots to test them.

diff --git a/build-configs.yaml b/build-configs.yaml
index 63e8184..1517eac 100644
--- a/build-configs.yaml
+++ b/build-configs.yaml
@@ -733,6 +733,46 @@ build_configs:
     branch: 'linux-5.3.y'
     variants: *stable_variants
 
+  stable-queue_4.4:
+    tree: stable-rc
+    branch: 'queue/4.4'
+    variants: *stable_variants
+    reference:
+      tree: stable
+      branch: 'linux-4.4.y'
+
+  stable-queue_4.9:
+    tree: stable-rc
+    branch: 'queue/4.9'
+    variants: *stable_variants
+    reference:
+      tree: stable
+      branch: 'linux-4.9.y'
+
+  stable-queue_4.14:
+    tree: stable-rc
+    branch: 'queue/4.14'
+    variants: *stable_variants
+    reference:
+      tree: stable
+      branch: 'linux-4.14.y'
+
+  stable-queue_4.19:
+    tree: stable-rc
+    branch: 'queue/4.19'
+    variants: *stable_variants
+    reference:
+      tree: stable
+      branch: 'linux-4.19.y'
+
+  stable-queue_5.4:
+    tree: stable-rc
+    branch: 'queue/5.4'
+    variants: *stable_variants
+    reference:
+      tree: stable
+      branch: 'linux-5.4.y'
+
   stable-rc_3.18:
     tree: stable-rc
     branch: 'linux-3.18.y'

[gctucker]

Ah, there used to be an issue with / characters in branch names because they would mess up the path on the storage server which includes the branch name. It should be fixed now, but this would be the first branches to actually have a slash in their names used in production so a bit more testing will be required to check the binaries all land in the right place etc...