fix(deps) Upgrade apollo federation with subgraph

[iMobs]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: #1782

What is the new behavior?

Directives and printSchema (now renamed printSubgraphSchema) are imported from the @apollo/subgraph module instead of from @apollo/federation.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

Recently the @apollo/subgraph module was created and split off from the @apollo/federation module (PR) and released that as a patch update. This broke using @nestjs/graphql with the newest version of @apollo/federation. The most obvious problem was with the optional import of directives reported in #1782.

I believe this overlaps and resolves the same issue as #1780 since this fixes the federation use of printSchema without changing the normal use of printSchema.

Closes #1782

[iMobs]

Looking again at where @apollo/federation is used, it could be replaced entirely with @apollo/subgraph since the only thing still in use is buildFederatedSchema which is deprecated and a re-export of buildSubgraphSchema. This seems like a more drastic step so I'll wait for initial feedback.

[kamilmysliwiec]

Looking again at where @apollo/federation is used, it could be replaced entirely with @apollo/subgraph since the only thing still in use is buildFederatedSchema which is deprecated and a re-export of buildSubgraphSchema. This seems like a more drastic step so I'll wait for initial feedback.

Agree. Would you like to create a follow-up PR that entirely replaces the @apollo/federation package? We'll surely merge it (eventually!)

I'll merge this one shortly, thanks!

[ssukienn]

@iMobs Just for reference this or follow-up PRs are not resolving #1780 case because in the place of "schema to file generation" (GraphQLSchemaBuilder.buildSchema) there is still used printSchema of graphql package instead of apollo federation or subgraph. Compare the changes and you will see that they do not overlap (not completely at least).