Remove dead arguments code

[basil]

The release build sets -Darguments in various places in a futile attempt to reduce log spam, futile because that setting is ignored due to the presence of https://github.com/jenkinsci/jenkins/blob/d25704cfbc929bca3bd5e5675e1fe1aa1a58928c/pom.xml#L429, as one can see by looking at the actual console output and seeing the log spam. And furthermore, the presence of custom arguments anywhere (either via -Darguments in the top-level Maven invocation or in the maven-release-plugin configuration in pom.xml) seems to break the release:stage goal in Maven Release Plugin 3.x as described in jenkins-infra/helpdesk#3143 (comment), so removing this dead code takes us one step closer toward working around the problem (the other step being removing the custom configuration in pom.xml).

[daniel-beck]

Since JDK 11 the log output is a joke anyway.

[NotMyFault]

👏🏻

[basil]

Since JDK 11 the log output is a joke anyway.

I do not see how JDK 11 would have changed anything. Seems like this has always been dead code since the day it was written, given how core's pom.xml had an arguments directive that superseded whatever was passed in here via -Darguments. MRELEASE-1048 was fixed, so presumably once the Maven folks fix the arguments issue, we could then pass -Darguments='--no-transfer-progress' to avoid the log spam (now that we eliminated any custom arguments from core's pom.xml).