trigger_gsc_signing.py: move to release bb bucket

We're moving our release operations (including signing) to be homed
under their own swarming pool, service accounts, and luci bucket.

This allows us more granular control of who can schedule builds and
write to different locations (gs buckets primarily).

BUG=chromium:1122854
TEST=./run_tests.py

Cq-Depend: chrome-internal:3575083
Change-Id: Ieb262705efa73d8f5c82d8356d7bbe920f0c2794
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/chromite/+/2660158
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: LaMont Jones <lamontjones@chromium.org>
Tested-by: George Engelbrecht <engeg@google.com>
Auto-Submit: George Engelbrecht <engeg@google.com>
diff --git a/scripts/trigger_gsc_signing.py b/scripts/trigger_gsc_signing.py
index 155afb2..e91f4d2 100644
--- a/scripts/trigger_gsc_signing.py
+++ b/scripts/trigger_gsc_signing.py
@@ -26,7 +26,7 @@
 assert sys.version_info >= (3, 6), 'This module requires Python 3.6+'
 
 
-GSC_PRODUCTION_JOB = 'chromeos/packaging/sign-image'
+GSC_PRODUCTION_JOB = 'chromeos/release/sign-image'
 GSC_STAGING_JOB = 'chromeos/staging/staging-sign-image'
 _IMAGE_TYPE = 'gsc_firmware'