Adding `deferSpec=20220824` to response headers breaks the Preview pane in browser devtools
### Issue Description

As I was working on improving the `@defer` support for Next.js in https://github.com/apollo-server-integrations/apollo-server-integration-next/pull/204 I noticed that when I viewed the Preview pane in Chrome devtools, it was always blank.

![image](https://github.com/user-attachments/assets/c0e8af2e-30bb-4d51-b133-017dcb4ab0a3)

I thought it might be something going on with Next.js, but I believe it is an issue with the headers being set here https://github.com/apollographql/apollo-server/blob/main/packages/server/src/runHttpQuery.ts#L305.

```
  graphQLResponse.http.headers.set(
    'content-type',
    'multipart/mixed; boundary="-"; deferSpec=20220824',
  );
```

In my Next.js app, I rewrote the headers to be
```
    const headers: Record<string, string> = {
      'content-type': 'multipart/mixed; boundary="-"',
    };
```

And the data appears in the Preview pane
![image](https://github.com/user-attachments/assets/afdf6335-d0a8-438c-b41d-3d3be4cd7e22).

Is there any reason to add the `deferSpec=20220824` to the response header? Without it Apollo Client behaves properly and the devtools are able to preview the response data.

### Link to Reproduction

https://github.com/apollo-server-integrations/apollo-server-integration-next/pull/204

### Reproduction Steps

I linked to the PR from the Next.js integration where I detailed all of this. I also have a project https://github.com/jer-k/graphql-rsc-dashboard which has a local version of `@as-integrations/next` installed where I'm testing this. I can create a branch of this project that sets everything up to be pulled down if need be.