Fragments should generate their own structs

When generating a client using fragments and lots of similar queries that use the same fragment it leads to lots of the same structs being generated.

Ideally there would be a seperate Fragments struct that contains the defined fragments.

I.e the following queries would both share the same response structs as they use the same fragment:

fragment LoadInfo on Load {
    loadId
    jobContainerId
    name
    loadPlanStatus
    journey {
        journeyId
    }
}

query loadById($load: Int!) {
    loadByID(loadId: $load) {
        ...LoadInfo
    }
}

query loadBySupplier($supplier: String!, $after: LocalDateTime!) {
    loadsBySupplierId(supplierCode: $supplier, after: $after) {
        ...LoadInfo
    }
}

Not sure how feasible that is, but I think something similar is done for input types and enums?

No se nombran archivos, pruebas ni puntos de entrada. Empieza trazando cómo el generador gestiona actualmente los tipos de entrada y los enums, y después define cómo se emiten y reutilizan las structs propias de los fragments; el trabajo estará terminado cuando ambas consultas de ejemplo compartan las structs de respuesta del fragment sin definiciones duplicadas.