Add support for custom OSSRH_USER value

This is now important because apparently it is no longer allowed to
deploy to OSS Sonatype (at least not s01.oss.sonatype.org) using the
plain username and password configuration -- only with the user token.
And the token has different alphabet gobbledegook for the username.

Author: ctrueden

ci-build.sh

@@ -80,6 +80,9 @@ if [ -f pom.xml ]; then
 	elif [ -f "$customSettings" ]; then
 		cp "$customSettings" "$settingsFile"
 	else
+		if [ -z "$OSSRH_USER" ]; then
+			OSSRH_USER=scijava-ci
+		fi
 		cat >"$settingsFile" <<EOL
 <settings>
 	<servers>
@@ -95,7 +98,7 @@ if [ -f pom.xml ]; then
 		</server>
 		<server>
 			<id>sonatype-nexus-releases</id>
-			<username>scijava-ci</username>
+			<username>$OSSRH_USER</username>
 			<password>$(escapeXML "$OSSRH_PASS")</password>
 		</server>
 	</servers>

github-actionify.sh

@@ -129,6 +129,7 @@ process() {
           GPG_PASSPHRASE: \${{ secrets.GPG_PASSPHRASE }}
           MAVEN_USER: \${{ secrets.MAVEN_USER }}
           MAVEN_PASS: \${{ secrets.MAVEN_PASS }}
+          OSSRH_USER: \${{ secrets.OSSRH_USER }}
           OSSRH_PASS: \${{ secrets.OSSRH_PASS }}
           SIGNING_ASC: \${{ secrets.SIGNING_ASC }}"