Jenkinsfile: Re-enable production checks but prevent bug filing

Bring back the automatic check for production builds so that images are put in
their main location and test jobs are submitted to LAVA, but mangle the LAVA
webhook callback URL so that we don't create too much noise in Phabricator at
this point.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Jenkinsfile

@@ -7,7 +7,7 @@ release = "next"
 /* Determine whether to run uploads based on the prefix of the job name; in
  * case of apertis we expect the official jobs under apertis-<release>/ while
  * non-official onces can be in e.g. playground/ */
-def production = false //env.JOB_NAME.startsWith("${osname}-")
+def production = env.JOB_NAME.startsWith("${osname}-")
 
 docker_registry_name = 'docker-registry.apertis.org'
 docker_image_name = "${docker_registry_name}/apertis/apertis-19.03-image-builder"
@@ -209,7 +209,7 @@ def submitTests(architecture, type, board, ostree = false) {
       -g apertis-tests/templates/profiles.yaml \
       --profile ${profile_name} \
       --callback-secret ${token} \
-      --callback-url https://lavaphabbridge.apertis.org/ \
+      --callback-url HACK-TO-TEMPORARILY-DISABLE-BUG-REPORTING-https://lavaphabbridge.apertis.org/ \
       -t release:${release} \
       -t image_date:${version} \
       -t image_name:${image_name}""")