upgrade testing: allow configurable artifactory repo (#25350)

Prerelease builds are in a different Artifactory repository than release
builds. Make this a variable option so we can test prerelease builds in the
nightly/weekly runs.

enos/enos-scenario-upgrade.hcl

@@ -48,6 +48,7 @@ scenario "upgrade" {
     variables {
       artifactory_username   = var.artifactory_username
       artifactory_token      = var.artifactory_token
+      artifactory_repo       = var.artifactory_repo_start
       arch                   = local.arch
       edition                = matrix.edition
       product_version        = var.product_version
@@ -242,6 +243,7 @@ scenario "upgrade" {
     variables {
       artifactory_username = var.artifactory_username
       artifactory_token    = var.artifactory_token
+      artifactory_repo     = var.artifactory_repo_upgrade
       arch                 = local.arch
       edition              = matrix.edition
       product_version      = var.upgrade_version

enos/enos-vars.hcl

@@ -27,12 +27,28 @@ variable "product_version" {
   default     = null
 }
 
+variable "artifactory_repo_start" {
+  description = "The Artifactory repository we'll download the starting binary from"
+  type        = string
+
+  # note: this default only works for released binaries
+  default = "hashicorp-crt-staging-local*"
+}
+
 variable "upgrade_version" {
   description = "The version of Nomad we want to upgrade the cluster to"
   type        = string
   default     = null
 }
 
+variable "artifactory_repo_upgrade" {
+  description = "The Artifactory repository we'll download the upgraded binary from"
+  type        = string
+
+  # note: this default only works for released binaries
+  default = "hashicorp-crt-staging-local*"
+}
+
 variable "download_binary_path" {
   description = "The path to a local directory where binaries will be downloaded to provision"
 }