JENKINS-72386: replace --no-transfer-progress option

[cronik]

-ntp is not supported on versions of maven prior to 3.6.1. Maven does exits with "unrecognized option" when it encounters an option it doesn't know about.

This solution uses replaces the unsupported option with a system property to reduce the transfer logger used for batch mode to WARN only. See MRELEASE-1048

Fixes JENKINS-72386 introduced by #716

Testing done

Tested 3.6 and 3.9 does not output transfer logs with alternate setting.

### Submitter checklist
- [x] Make sure you are opening from a **topic/feature/bugfix branch** (right side) and not your main branch!
- [x] Ensure that the pull request title represents the desired changelog entry
- [x] Please describe what you did
- [x] Link to relevant issues in GitHub or Jira
- [x] Link to relevant pull requests, esp. upstream and downstream changes
- [ ] Ensure you have provided tests - that demonstrates feature works or fixes the issue

[cronik]

@bguerin any chance this PR can be adopted in place of --no-progress-transfer? it has the same out outcome and is backwards compatible.

[bguerin]

Hello @cronik

Thanks for your work. I did not expect to still have to deal with more than 4 years old Maven versions (3.6.1 was out on april 2019).
I will not follow this way as it uses internals of Maven. Quoting maven-release-plugin is not an argument from my point of view. The release plugin and Maven are the same project, they share parts of code, and maintainers of one can act on other if needed.

This Jenkins plugin is just using Maven, as you could do by hand in a scripted Jenkinsfile. I do not want to depend on internals of Maven, which could change or disappear.

I also have to solve some Jenkins CI issues if I want to upgrade to Maven 3.9 (handle MAVEN_ARGS env var), so I will close this PR in favor of another solution:
#749