Remove support for soon-to-be-deprecated user API calls

Due to privacy restrictions, the API will soon restrict the ability to retrieve user info using anything but an account ID. Finding users via other fields must go through /user/search. As such, getUser (which was already redundant with getUserByEmail) has been removed, and dependent procs updated to use getUserByEmail (which uses the /search endpoint).

Author: pclifton

package/main.tcl

@@ -492,31 +492,6 @@ namespace eval ::jira {
 			return 0
 		}
 	}
-
-	#
-	# Given a username (eg "fred"), get user data and store in _result
-	#
-	# See https://docs.atlassian.com/jira/REST/cloud/#api/2/user-getUser
-	#
-	proc getUser {key _result args} {
-		::jira::parse_args args argarray
-		upvar 1 $_result result
-		unset -nocomplain result
-
-		if {$key == ""} {
-			set url "[::jira::baseurl]/rest/api/2/myself"
-		} else {
-			set url "[::jira::baseurl]/rest/api/2/user?username=$key"			
-		}
-
-
-		if {[::jira::raw $url GET json]} {
-			array set result [::yajl::json2dict $json(data)]
-			return 1
-		} else {
-			return 0
-		}
-	}
 
 	#
 	# Given an email address, try to find a user with that address. This proc only
@@ -799,7 +774,7 @@ namespace eval ::jira {
 			return
 		}
 
-		::jira::getUser $key getUserResult
+		::jira::getUserByEmail $key getUserResult
 
 		set keyMap [list self displayName active]