Add graphqlQueriesPath customisation option to the config.client

[coreyaus]

Notes

• In particular this is useful for mono-repos needing to support custom queries within each package/sub-folder as well as shared base queries at the root level.
• This configuration option is intended to allow users to provide a path to where their custom GraphQL /queries folder(s) can be found.
  • It supports files with the following extensions: *.{graphql,gql}
  • One use case is to support patterns matching multiple folder paths, e.g. if working in a mono-repo and needing to support custom queries within each package/sub-folder as well as shared base queries at the root level. An example of that can be achieved by setting the graphqlQueriesPath customisation option to a value like the following:

    root-path/{sub-path/,}tina`

• Heads up @logan-anderson this is one of the small tweaks we discussed (though to be honest I haven't tested it in this exact format - we just set the userQueriesAndFragmentsGlob value directly in our code via a Yarn patch, so this is the first attempt by properly exposing a config option). No dramas if this doesn't suit with your plans though!

[changeset-bot]

🦋 Changeset detected

Latest commit: 665c949

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

This PR includes changesets to release 21 packages

Name	Type
@tinacms/schema-tools	Patch
@tinacms/cli	Patch
tinacms-authjs	Patch
tinacms	Patch
@tinacms/graphql	Patch
@tinacms/mdx	Patch
@tinacms/search	Patch
starter-basic-iframe	Patch
starter-empty	Patch
e2e-next	Patch
@tinacms/self-hosted-starter	Patch
kitchen-sink-starter	Patch
@tinacms/starter	Patch
next-tinacms-cloudinary	Patch
next-tinacms-dos	Patch
next-tinacms-s3	Patch
tinacms-clerk	Patch
@tinacms/app	Patch
@tinacms/vercel-previews	Patch
@tinacms/datalayer	Patch
tinacms-gitprovider-github	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