feat: RedisEventTarget

[n1ru4l]

• This moves the TypedEventTarget type into a standalon package @graphql-yoga/typed-event-target.
• Adds the @graphql-yoga/redis-event-target package which has a EventTarget implementation based on redis pub/sub using ioredis

Future thoughts:

• I used Event with a custom data attribute, and now I figured out that there is also CustomEvent, but it is still not available in the latest Node.js. Changing the API to use CustomEvent would be a breaking change, thus for now I kept re-using the Event. In the next major release, we can consider using CustomEvent instead.

---

Node.js Progress for supporting CustomEvent:

• Support CustomEvent nodejs/node#40678
• events: add CustomEvent nodejs/node#43514

Closes #1297

[changeset-bot]

🦋 Changeset detected

Latest commit: 9fff3b7

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

This PR includes changesets to release 4 packages

Name	Type
@graphql-yoga/typed-event-target	Minor
@graphql-yoga/subscription	Minor
@graphql-yoga/redis-event-target	Minor
example-redis-pub-sub	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% ✓ 229362      ✗ 0     
     data_received..................: 31 MB   1.0 MB/s
     data_sent......................: 13 MB   440 kB/s
     http_req_blocked...............: avg=1.1µs    min=800ns   med=1µs      max=234.5µs p(90)=1.4µs   p(95)=1.7µs   
     http_req_connecting............: avg=0ns      min=0s      med=0s       max=98.9µs  p(90)=0s      p(95)=0s      
   ✓ http_req_duration..............: avg=195.45µs min=136.5µs med=172.2µs  max=18.98ms p(90)=216.5µs p(95)=242.3µs 
       { expected_response:true }...: avg=195.45µs min=136.5µs med=172.2µs  max=18.98ms p(90)=216.5µs p(95)=242.3µs 
     http_req_failed................: 0.00%   ✓ 0           ✗ 114681
     http_req_receiving.............: avg=17.3µs   min=10.2µs  med=15.8µs   max=8.95ms  p(90)=20.1µs  p(95)=22.7µs  
     http_req_sending...............: avg=5.76µs   min=3.9µs   med=4.59µs   max=6.35ms  p(90)=6.3µs   p(95)=9.1µs   
     http_req_tls_handshaking.......: avg=0s       min=0s      med=0s       max=0s      p(90)=0s      p(95)=0s      
     http_req_waiting...............: avg=172.38µs min=118.6µs med=151.69µs max=18.9ms  p(90)=189.6µs p(95)=211.8µs 
     http_reqs......................: 114681  3822.517127/s
     iteration_duration.............: avg=256.93µs min=187.2µs med=229.3µs  max=19.4ms  p(90)=288.3µs p(95)=319.79µs
     iterations.....................: 114681  3822.517127/s
     vus............................: 1       min=1         max=1   
     vus_max........................: 1       min=1         max=1   

[github-actions]

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

@graphql-yoga/common@2.12.0-canary-8bcfabb.0
@graphql-yoga/redis-event-target@0.1.0-canary-8bcfabb.0
@graphql-yoga/typed-event-target@0.1.0-canary-8bcfabb.0
graphql-yoga@2.13.0-canary-8bcfabb.0
@graphql-yoga/node@2.13.0-canary-8bcfabb.0
@graphql-yoga/render-graphiql@2.13.0-canary-8bcfabb.0
@graphql-yoga/subscription@2.2.0-canary-8bcfabb.0

[n1ru4l]

Skipping because it is also broken on master. See #1378

[charlypoly]

@dotansimha @n1ru4l the SvelteKit integration has been broken in the following PR that introduced breaking changes in yoga/common: #1364