Handle Enum resolvers

[eddeee888]

Handle Enum resolvers generation, autowireup and custom mappers.

A by-product of this change is that enum resolver types are generated by default now to support a smoother type wireup. I think this is an acceptable trade-off because we want users to be able to create enum resolver files without having to add mappers/enumValues to trigger enum resolver type generation

(codegen behaviour is not to generate enum type resolvers unless these are used)

Related: https://github.com/eddeee888/graphql-code-generator-plugins/issues/265

[changeset-bot[bot]]

🦋 Changeset detected

Latest commit: af558cf42be4da8a31d2b48dcdb83fd61187ab69

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

This PR includes changesets to release 1 package

| Name | Type | | ---------------------------------------- | ----- | | @eddeee888/gcg-typescript-resolver-files | Minor |

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

[eddeee888]

/release-snapshot

[github-actions[bot]]

✅ Successfully published package/s with tag pr293-run533-1!

[eddeee888]

/release-snapshot

[github-actions[bot]]

✅ Successfully published package/s with tag pr293-run537-1!

[eddeee888]

/release-snapshot

[github-actions[bot]]

✅ Successfully published package/s with tag pr293-run538-1!