feat: added support for personal-access-tokens

[evilnerd]

• added a new PATAuthTransport type that has a 'Token' attribute to hold your unique PAT
• setting the Authorization header with the bearer token in the RoundTrip function.
• added test to prove to the token gets passed via the header
• bonus: fixed typo in existing test name

Resolves #421

Description

This PR adds support for authentication using Personal Access Tokens on Jira Data Center.

Information that is useful here:

• The What: It adds a new PATAuthTransport type which can be used to create a client that uses PATs to authenticate.
• The Why: Using PATs make it easier to run jobs on Jira automatically, without having to maintain usernames/passwords to get access to the on-premise Jira.
• Type of change: New feature
• Breaking change: No
• Related to an issue: This PR fixes issue 421
• Jira Version + Type: Jira DataCenter v8.20.1

Example:

// Create transport using the PersonalAccessToken specified in the password.
tp := client.PATAuthTransport {
		Token: password,
		Transport: &http.Transport{
			TLSClientConfig: &tls.Config{InsecureSkipVerify: true},
		},
	}

// Open the connection to Jira
jiraClient, err := jira.NewClient(tp.Client(), url)

Checklist

• [ x] Unit or Integration tests added
  • [x ] Good Path
  • Error Path
• [ x] Commits follow conventions described here:
  • [x ] Conventional Commits 1.0.0
  • [ x] The seven rules of a great Git commit message
• [ x] Commits are squashed such that
  • [x ] There is 1 commit per isolated change
• [ x] I've not made extraneous commits/changes that are unrelated to my change.