Feature/issue 1048 handle merging additional Request / Response properties

[thescientist13]

Related Issue

resolves #1048

Depends on #1131

Summary of Changes

1. Honor and merge all constructor options for Response
2. Honor body (.text(), .json() and formData()) and method on Request objects
3. "Lock down" content type header responses in test cases (Found that internal Font Resource plugin was not returning the correct content type - worth making a new issue?)
4. Added new test cases

TODO

1. Merge all applicable Request properties- Search page with POST and FormData examples thescientist13/greenwood-htmx#3
   • body
   • headers
   • query params
   • Others? - see Thoughts section below
2. Merge all applicable Response properties
   • status
   • statusText ?
3. Apply to all instance in serve lifecycle
   • return all header, like custom x-secret header in the POST /api/submit example in develop
4. executeRouteModule
   • API Routes
   • SSR page - I think the plan is to support this in Data Loading Strategies #952 ?
5. Apply to Adapter plugins
   • feature/issue 1008 netlify adapter plugin #1128
   • Feature/issue 1008 vercel adapter plugin #1139
6. Apply to SSR page bundled output? - https://github.com/ProjectEvergreen/greenwood/blob/v0.29.0-alpha.1/packages/cli/src/lifecycles/bundle.js#L224
   • already support Content-Type header, nothing else to support at the moment - https://github.com/ProjectEvergreen/greenwood/blob/v0.29.0-alpha.2/packages/cli/src/lifecycles/bundle.js#L226
7. Add test cases
8. POST w/ request.formData
   • and adapter plugins
9. Clean up console logs
10. Clean up TODO items
    • issues/1048
    • issues/1008
11. Documentation updates?
12. ~~multipart/form-data~~ support (nice to have)? - support additional Request.body formats #1147

Thoughts / Questions

1. We don't get much from each ctx.request from Koa, so we can't really flesh out more than this from an initial request. Not sure how much of a Request options is ultimately worth merging on or we can even support? Maybe a good discussion topic? - Web Standards Web Server (native `Request` / `Response` support) #1146

   CTX.REQUEST {
     method: 'GET',
     url: '/api/missing',
     header: { host: '127.0.0.1:8080', connection: 'close' }
   }

2. Could maybe add a tracking issue to validate all body options. Not sure how to best handle / detect them in Koa for serialization though? Options like: - support additional Request.body formats #1147
   • URLSearchParams
   • Blob