support new config option `mappersRelativeTargetDir`

[HunterLarco]

By default, mappers must be siblings with the schema they represent. For example, if the schema file is /path/to/schema.graphql, the mapper file is /path/to/schema.mappers.ts. This extension allows mappers to reside in a different directory relative to the schema file using the pattern <schemaPath>/<mappersRelativeTargetDir>/<schemaName><mappersFileExtension>. This is useful for users which prefer to locate mappers in their own directory rather than interspliced with the schema files.

Testing

• [x] unit tests in typescript-resolver-files are passing
• [x] e2e tests are passing. Note that I've updated a pre-existing e2e test which already tests every mapper option. I've added this new option to the test and validate that output looks as expected.
• [x] I've used a local build of this change in my own project and validated that the generated output builds and operates as expected.

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 1d4797222c96f1ce8146176081a970cebba74c9b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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