Unsupported content type when multipart chunk content-type contains anything more than just the type

[calvincestari]

Summary

Copied from #2395 (comment).

Based on the defer spec here, an example response body could look like the following:

/~https://github.com/graphql/graphql-over-http/blob/main/rfcs/IncrementalDelivery.md#content-type-multipartmixed

---
Content-Type: application/json; charset=utf-8

{"data":{"hello":"Hello Rob"},"hasNext":true}
---
Content-Type: application/json; charset=utf-8

{"data":{"test":"Hello World"},"path":[],"hasNext":false}
-----

As of right now, the code is only checking for
Content-Type to be application/json. This seems to cause problems and throws an unsupportedType error.

Version

1.15.3

Steps to reproduce the behavior

Receive a multipart chunk with a content type of Content-Type: application/json; charset=utf-8.

Logs

No response

Anything else?

No response

[calvincestari]

@brettephillips - the fix for this has been merged and will go out in the next release.