Fix paging with load balancer going to endless loop

[evilnerd]

PR Description

When used with a load balanced Jira, the SearchPages method would end
up in an endless loop. This was caused by a bug where Jira would not
handle the MaxResults=50 that is sent by defaul properly, thus retur-
ning no issues. The SearchPages method didn't check for empty results
and ended up in an endless loop.

Fixed this by

1. Pre-escaping '&maxResults' to '&MaxResults'.
2. Adding a check in SearchPages to see if the issues array is empty
   before going into the endless 'for'.

Also fixed the appropriate tests.

Fixes issue #260.

Checklist

• Tests added
  • Good Path
  • Error Path
• Commits follow conventions described here:
  • https://conventionalcommits.org/en/v1.0.0-beta.4/#summary
  • https://chris.beams.io/posts/git-commit/#seven-rules
• Commits are squashed such that
  • There is 1 commit per isolated change
• I've not made extraneous commits/changes that are unrelated to my change.

[ghostsquad]

@evilnerd your commit message is ALMOST perfect. Here's the only thing you need to change:

old:

Fix paging with load balancer

new:

fix: paging with load balancer

The commands to do this are simple though.

git commit --amend

git push --force

The first command will let you edit your commit message, which will change the commit sha, and require you to force push up to Github.

https://help.github.com/en/github/committing-changes-to-your-project/changing-a-commit-message

[evilnerd]

Made the change. Thanks again for your help!