sbt-deploy-to.sh requires the target repository to be explicitly specified

`sbt-deploy.sh` assumes that all artifacts will be published to a public location at artifactoryonline (`ext-releases-local`). However, private artifacts should instead be published to a different, private location.

Two changes have been introduced:

  1. A new script, `sbt-deploy-to.sh` has been created. This script accepts the target repository as a command-line argument (as well as optional multiple-project names, the same as the original script).
  2. The original script, `sbt-deploy.sh`, has been decorated with deprecation warnings, so that people can migrate to `sbt-deploy-to.sh`. Once other builds have migrated, we will have uniformity in the sbt-deploy process.