Explicitly publish release and version info

Rather than bundle the release and version info file updates with the publish lifecycle task, require that they be run explicitly to update (as part of the release process, for example)

Author: lesserwhirls

gradle/root/publishing.gradle

@@ -127,8 +127,6 @@ def publishReleaseInfoTask = tasks.register('publishReleaseInfo', PublishToRawRe
     }
 }
 
-publish.dependsOn publishReleaseInfoTask
-
 def publishVersionInfoTask = tasks.register('publishVersionInfo', PublishToRawRepoTask) {
     group = 'publishing'
     description = 'Publish version-info.json to Nexus docs.'
@@ -146,8 +144,6 @@ def publishVersionInfoTask = tasks.register('publishVersionInfo', PublishToRawRe
     }
 }
 
-publish.dependsOn publishVersionInfoTask
-
 // The "publish" tasks for all subprojects require credentials for our Nexus server, which they look for in Gradle
 // properties. If those properties (i.e. NEXUS_USERNAME_KEY and NEXUS_PASSWORD_KEY) haven't been provided, the build
 // will fail. Therefore, we only want to configure credentials when a "publish" task is part of the execution plan.