Fix status code and json request normalization

[maxb08]

Description

Two fixes:

1. Status code was not being passed along due to improper nesting + parameters to the Request constructor.
2. Change normalize request so that any application/json request types send the body to mock handler as an object instead of a string. Express sends as an object so there's a discrepancy where the mocks receive two different data types depending on where they're run.

Motivation and Context

Ensure compatibility of mocks written for parrot-middleware with parrot-fetch.

How Has This Been Tested?

Unit tests + manual verification

Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation (adding or updating documentation)
• Dependency update

Checklist:

• My change requires a change to the documentation and I have updated the documentation accordingly.
• My changes are in sync with the code style of this project.
• There aren't any other open Pull Requests for the same issue/update.
• These changes should be applied to a maintenance branch.
• This change requires cross browser checks.
• This change impacts caching for client browsers.
• I have added the Apache 2.0 license header to any new files created.

What is the Impact to Developers Using parrot?

parrot-fetch should now be more compatible with parrot-middleware mocks.

[CLAassistant]

All committers have signed the CLA.

[maxb08]

Can't reproduce the node 16 runner result locally while trying to match all versions, very odd (same node+npm & npm ci)

edit: found it. Must be that we're failing on unhandled promise rejections (iirc it's opt in for node 16), and I forgot to await on expect(...).resolves.toBe