client:check only prints the filename of the first merged definition

**Intended outcome:**

We use the client:check utility in our pull requests to verify that the code in the pull request is compatible with the version of our graphql server that is currently deployed in different environments.
After running it, we check the list of failures against the files changed in the PR and only report a failure on that PR if one of the files changed in the PR was flagged as having an incompatibility.

When an operation that uses fragments has an incompatibility, it only prints the file path of the first included fragment.

**Actual outcome:**

The file names of all definitions that were merged to form the document are printed.

**How to reproduce the issue:**

Have an operation that uses at least 1 fragment. Introduce a change to the operation that is incompatible with a published service, run the client check. Observe that the fragment file path is printed

**Versions**

2.33.4

Start at the client:check entry point and reproduce the fragment-based incompatibility described in the issue. Trace how merged definitions are associated with filenames, then verify the output against the issue's intended listing of definition files. Done means the reported filenames are consistent for operations that include fragments.

Written by the indexing model from the issue text.