[FIXED JENKINS-24341] - Check if the project can be disabled before the disabling

The change call the AbstractProject::supportsMakeDisabled() before calling AbstractProject::makeDisabled()

Signed-off-by: Oleg Nenashev <o.v.nenashev@gmail.com>
Remove jenkins svnkit in favor of default svnkit library.
Fixed unit tests where resulting revision string contains a lower case A.
Fixed ClassCastException with DefaultAuthenticationManager.
Proper fix for DefaultSVNAuthenticationManager. Currently the default version in svnkit ignores any added authentication methods other than the three default items. This fix ignores any authentications that are stored on disk or persisted to memory. Since we create our own authentication, we should ignore the default items and use our own instead.
If there is an already existing svnserve instance running, fail the build.
Fixed test unit.
Use assertLogContains instead of manually scanning logs.
Fixed license headers and added COPYING file with license. Moved svnkit specific elements in to another package.
Renamed ISVNAuthenticationManager to a simpler name.
The list subversion tags parameter should consider the Item.BUILD permission and not Item.CONFIGURE
Add some null safety
Revert "Add some null safety"

This reverts commit b563d821e56bf43d5e8df10abdc3bf526a9843d3.
[SECURITY-158] Fixing doFillCredentialsIdItems for SubversionTagAction.
Amends 399f17a.
[SECURITY-158] checkCredentialsId/fillCredentialsIdItems cannot be called on a null context.
Amends 399f17a.
Comment.
[SECURITY-158] checkCredentialsId/fillCredentialsIdItems were not actually being used as intended.
Amends 399f17a.
User is allowed to bring their own credentials. If they have Item.CONFIGURE then they can use Jenkins credentials for tagging also
[maven-release-plugin] prepare release subversion-2.5-beta-3
[maven-release-plugin] prepare for next development iteration