Fix path matching types getting lost in recursive types

[jpwilliams]

Summary

Fixes a "Type instantiation is excessively deep and possibly infinite" bug when attempting to generate paths for events with recursive types, such as a common JsonValue type.

type JsonObject = { [Key in string]?: JsonValue };
type JsonArray = Array<JsonValue>;
type JsonValue =
  | string
  | number
  | boolean
  | JsonObject
  | JsonArray
  | null;

We refactor the way paths are generated a little here, most notably ensuring we skip known deep/recursive types and don't needlessly iterate those we've seen before.

Checklist

• [ ] Added a docs PR that references this PR N/A Bug fix
• [x] Added unit/integration tests
• [x] Added changesets if applicable

[changeset-bot[bot]]

🦋 Changeset detected

Latest commit: 3e516eef3c67faac1421d55912378f7027aadded

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

This PR includes changesets to release 1 package

| Name | Type | | ------- | ----- | | inngest | 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

[inngest-release-bot]

A user has added the prerelease/inngest label, so this PR will be published to npm with the tag pr-354. It will be updated with the latest changes as you push commits to this PR.

You can install this prerelease version with:

npm install inngest@pr-354

The last release was built and published from 3e516eef3c67faac1421d55912378f7027aadded.