Invoke-GHRestMethod - Find way to avoid duplicating codepaths for Status vs NoStatus

[HowardWolosky]

This was mentioned by @danbelcher-MSFT during the PR for #60. Right now, we have a bit of duplicated code for how we execute the request synchronously (with -NoStatus) vs asynchronously with command-prompt status updates.

We should look to see if we can define the command-block of common code once, and then re-use it in both scenarios.

[HowardWolosky]

One potential way to solve this is to always use a job to execute the request, and simply use $NoStatus to determine if wait for the result with Wait-Job or Wait-JobWithAnimation.

[HowardWolosky]

#253 changed how we handle status, and so this is no longer applicable. There is no longer any duplicated code since we don't have bifurcating paths based on status.