feat: populate GaxiosResponse with raw response information (res.url)

[marapper]

To resolve #187

Adding request.responseUrl with real URL after redirects to response.

await axios.get('/redirect')

{
 config: {
   url: '/redirect',
   ...
 },
 request: {
   responseURL: 'https://example.com/real_page',
 }
}

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[marapper]

@googlebot I signed it!

[googlebot]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[bcoe]

@marapper don't worry about the license header, not your issue; thanks for the patch.

[codecov]

Codecov Report

Merging #189 into master will increase coverage by 0.05%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #189      +/-   ##
==========================================
+ Coverage   96.59%   96.64%   +0.05%     
==========================================
  Files           4        4              
  Lines         587      597      +10     
  Branches      100      100              
==========================================
+ Hits          567      577      +10     
  Misses         19       19              
  Partials        1        1

Impacted Files	Coverage Δ
src/gaxios.ts	93.46% <100%> (+0.12%)	⬆️
src/common.ts	100% <100%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ba9777b...2d82b21. Read the comment docs.

[bcoe]

one thing jumps out at me in final review, why populate status and statusText twice, if we already have them on the top level object?

[marapper]

Yes, I just forgot to remove it. In axios it is populating twice but I think it's redundant.

Updated.

[googlebot]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[bcoe]

@marapper thank you for the contribution \o/ this will be released shortly after the holidays.