[federation] add utility to fetch managed federation supergraph

[EmrysMyrddin]

Description

This PR implement a fetcher to build a stitched schema from GraphOS managed federation.

fixes #6226

Type of change

• New feature (non-breaking change which adds functionality)

[changeset-bot]

🦋 Changeset detected

Latest commit: 7e6b24e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@graphql-tools/federation	Patch
federation-benchmark	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

✅ Benchmark Results

     ✓ no_errors
     ✓ expected_result

     checks.........................: 100.00% ✓ 342       ✗ 0  
     data_received..................: 40 MB   4.0 MB/s
     data_sent......................: 146 kB  15 kB/s
     http_req_blocked...............: avg=3.89µs   min=2.09µs   med=2.57µs  max=172.07µs p(90)=3.81µs   p(95)=3.99µs  
     http_req_connecting............: avg=676ns    min=0s       med=0s      max=115.7µs  p(90)=0s       p(95)=0s      
     http_req_duration..............: avg=54.33ms  min=47.23ms  med=50.36ms max=145.16ms p(90)=57.07ms  p(95)=84.62ms 
       { expected_response:true }...: avg=54.33ms  min=47.23ms  med=50.36ms max=145.16ms p(90)=57.07ms  p(95)=84.62ms 
     http_req_failed................: 0.00%   ✓ 0         ✗ 171
     http_req_receiving.............: avg=136.35µs min=104.02µs med=129.4µs max=683.04µs p(90)=146.77µs p(95)=155.52µs
     http_req_sending...............: avg=26.05µs  min=16.53µs  med=25.26µs max=101.05µs p(90)=30.18µs  p(95)=34.95µs 
     http_req_tls_handshaking.......: avg=0s       min=0s       med=0s      max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=54.17ms  min=47.07ms  med=50.2ms  max=144.41ms p(90)=56.89ms  p(95)=84.47ms 
     http_reqs......................: 171     17.096566/s
     iteration_duration.............: avg=58.47ms  min=50.83ms  med=54.42ms max=149.14ms p(90)=62.93ms  p(95)=88.7ms  
     iterations.....................: 171     17.096566/s
     vus............................: 1       min=1       max=1
     vus_max........................: 1       min=1       max=1

[github-actions]

💻 Website Preview

The latest changes are available as preview in: https://6d598355.graphql-tools.pages.dev

[github-actions]

🚀 Snapshot Release (alpha)

The latest changes of this PR are available as alpha on npm (based on the declared changesets):

Package	Version	Info
@graphql-tools/federation	1.1.37-alpha-20240604080225-7e6b24e313ccf7c34d5814aee98d58a244c2e129	npm ↗︎ unpkg ↗︎

[ardatan]

Just an idea... This can be an event target and it can emit events such as schema, error, message etc instead of onSchemaChange, onFailure and logger.

[ardatan]

For type safety, it can even use something like this;
https:/dotansimha/graphql-yoga/blob/main/packages/event-target/typed-event-target/src/index.ts

[EmrysMyrddin]

I've tried to do it. I really dislike the API of dotansimha/graphql-yoga@main/packages/event-target/typed-event-target/src/index.ts. It's tight to DOM usage which make it much less clear how to use it.

I've tried a implementation based on EventEmitter which works pretty great, but it's then tight to Node, which means it would make this work only in Node environment, or I have to make a cross-plateform polyfill for it.