Bug 1842403 - Fix release-next regex for update-verify-next tests on 115esr. r=dandarnell

release-update-verify-next tests on comm-esr115 will not include 102.x.y versions
when testing unless the regex matches.
Balrog rule 17775 facilitates these tests on the comm-release-localtest-next
channel. It will be updated at release time via the "thunderbird-release115-localtest-next"
alias.

Differential Revision: https://phabricator.services.mozilla.com/D183079

--HG--
extra : moz-landing-system : lando

taskcluster/ci/release-balrog-submit-toplevel/kind.yml

@@ -43,7 +43,7 @@ jobs:
             rules-to-update:
                 by-release-type:
                     beta: ["thunderbird-beta-cdntest", "thunderbird-beta-localtest"]
-                    release: ["thunderbird-release115-cdntest", "thunderbird-release115-localtest"]
+                    release: ["thunderbird-release115-cdntest", "thunderbird-release115-localtest", "thunderbird-release115-localtest-next"]
                     default: []
             platforms: ["linux", "linux64", "macosx64", "win32", "win64"]
         treeherder:

taskcluster/comm_taskgraph/transforms/update_verify_config.py

@@ -27,7 +27,7 @@ INCLUDE_VERSION_REGEXES = {
     "beta": r"'^(\d+\.\d+b\d+)$'",
     "nonbeta": r"'^\d+\.\d+(\.\d+)?$'",
     # Previous major versions, for update testing before we update users to a new esr
-    "release-next": r"'^91\.\d+(\.\d+)?$'",
+    "release-next": r"'^(91|102)\.\d+(\.\d+)?$'",
 }
 
 MAR_CHANNEL_ID_OVERRIDE_REGEXES = {