Using fragments in combination with `PreloadQuery` leads to `unique-names` warnings

# What's the matter?
When using the [PreloadQuery](https://github.com/apollographql/apollo-client-nextjs#preloading-data-in-rsc-for-usage-in-client-components) component with a query that contains fragments, we get following `unique-names` warning in the console:

```
Warning: fragment with name Compoany already exists.
graphql-tag enforces all fragment names across your application to be unique; read more about
this in the docs: http://dev.apollodata.com/core/fragments.html#unique-names
```
# What do we expect?
Using `PreloadQuery` should not lead to `unique-names` warnings.

Also: The links is not very helpful because the page doesn't exist anymore.

# How to reproduce?
Take a look into the console of following example https://stackblitz.com/edit/nextjs-869gd8?file=app%2Fexample-query.ts,app%2Fpage.tsx

The reproduction uses app/example-query.ts and app/page.tsx in the linked StackBlitz; start there and inspect the PreloadQuery path for fragment handling. Reproduce the console warning, then verify the example runs without unique-names warnings and that the referenced documentation link is current.

Written by the indexing model from the issue text.