Fix exception when invoked from TFS Release Management (JENKINS-40283)

[davidstaheli]

This addresses issue JENKINS-40283 that addresses a crash with the following stack trace:

java.lang.Error: java.net.URISyntaxException: Cannot parse Git URI-ish: The uri was empty or null
	at hudson.plugins.tfs.model.GitCodePushedEventArgs.getRepoURIish(GitCodePushedEventArgs.java:23)
	at hudson.plugins.tfs.CommitParameterAction.<init>(CommitParameterAction.java:20)
	at hudson.plugins.tfs.model.BuildCommand.contributeTeamBuildParameterActions(BuildCommand.java:227)
	at hudson.plugins.tfs.model.BuildCommand.perform(BuildCommand.java:110)

Tested as follows:

1. mvn clean verify - All tests pass
2. I verified failure with the above stack trace when the "Jenkins Queue Job" task invoked a Jenkins job from TFS Release Management. Then, I applied this code change and verified that the job ran successfully.

[AlexRukhlin]

LGTM

[olivierdagenais]

Is Build.Repository.Uri present in the JSON payload and has an empty/null value or is it not present at all? For example, line 207 above checks if the map contains an entry with what resolves to the Build.Repository.Provider key.

Otherwise, might I recommend using org.apache.commons.lang.StringUtils.isNotBlank()?

[davidstaheli]

Build.Repository.Uri is present in the JSON payload and ends up having a value of white space. So unfortunately, we can't use teamBuildParameters.containsKey(BUILD_REPOSITORY_URI). Great suggestion to use org.apache.commons.lang.StringUtils.isNotBlank(). I made that change. Does it look okay otherwise @olivierdagenais?

[olivierdagenais]

Thank you for your contribution, you may merge at your convenience.