architect the graphql files folder structure

[gosuto-inzasheru]

          nomenclature might be a bit confusion, but doing a bit of research on the react-f/e directory structure components living in `queries/` are those reading from on-chain, triggering txs, use to call subgraphs, endpoints etc (seems the "ideal" state for abstracting that logic) and then importing those in `components/`

however, what i realised regarding the "query" itself *.graphql files. it is that it could live in subgraphs/smartgarden-optimism-gauges/graphql (queries scope per subgraph) and then using the right config for codegen.yml. It could auto-generate the function helpers that we could import later on the queries/ files from subgraphs/smartgarden-optimism-gauges/generated/graphql.tsx. in that way all (gql, *.graphql) will be isolated per subgraph directory we have and then elsewhere could be imported from there

we will need to investigate if that could be create out of the box using, something from this or combination of:

• @graphql-codegen/cli
• @graphql-codegen/typescript
• @graphql-codegen/typescript-react-query

Originally posted by @petrovska-petro in #25 (comment)

[gosuto-inzasheru]

to be frank, for me it feels more logical for the gql queries to live in the frontend folder, since they are part of the frontend. the subgraphs folders can then be thought of as the backend.

lets see, not sure i understand your codegen.yml idea.