Rename Central Portal deployment env vars

OK, now I'm renaming the credentials, because my first release failed:

  Error: [ERROR] Unable to upload bundle for deployment: Deployment
  [INFO] java.lang.RuntimeException: Invalid request. Status: 401 Response body:
  [INFO]     at org.sonatype.central.publisher.client.httpclient.UploadPublisherEndpoint.call (UploadPublisherEndpoint.java:33)

I am not actually certain the user token changed (it may just be
that the legacy `OSSRH_USER=scijava-ci` value was the culprit), but
that's OK: going through the few orgs that actually deploy to Maven
Central to update to a new token is not really such a big hassle.

Author: ctrueden

ci-build.sh

@@ -75,14 +75,14 @@ if [ -f pom.xml ]; then
 	mkdir -p "$HOME/.m2"
 	settingsFile="$HOME/.m2/settings.xml"
 	customSettings=.ci/settings.xml
-	if [ -z "$MAVEN_PASS" -a -z "$OSSRH_PASS" ]; then
+	if [ "$OSSRH_USER" -o "$OSSRH_PASS" ]; then
+		echo "[WARNING] Obsolete OSSRH vars detected. Secrets may need updating to deploy to Maven Central."
+	fi
+	if [ -z "$MAVEN_PASS" -a -z "$CENTRAL_PASS" ]; then
 		echo "[WARNING] Skipping settings.xml generation (no deployment credentials)."
 	elif [ -f "$customSettings" ]; then
 		cp "$customSettings" "$settingsFile"
 	else
-		if [ -z "$OSSRH_USER" ]; then
-			OSSRH_USER=scijava-ci
-		fi
 		cat >"$settingsFile" <<EOL
 <settings>
 	<servers>
@@ -98,8 +98,8 @@ if [ -f pom.xml ]; then
 		</server>
 		<server>
 			<id>central</id>
-			<username>$OSSRH_USER</username>
-			<password>$(escapeXML "$OSSRH_PASS")</password>
+			<username>$CENTRAL_USER</username>
+			<password>$(escapeXML "$CENTRAL_PASS")</password>
 		</server>
 	</servers>
 	<profiles>