Prevent GraphQL Queries from Impacting Common Codegened Names

[harrysolovay]

Seems new queries sometimes result in differently named types in the codegen. For instance Account -> Account2 upon introduction of mempool queries. Also affected: DaemonStatus -> DaemonStatus3.

[harrysolovay]

The issue comes from multiple queries that specify different selection sets on the same object. The end result is different structs representing those different selection sets. Unfortunately, this compromises our ability to use a single Into implementation for the same objects (even if they select all the same data required by the implemented fn into). This could potentially be addressed by obmarg/cynic#1015. In the meantime, we can just use fragments for common selection sets.

[harrysolovay]

We need a new cynic release in order to be able to use fragments on interfaces such as UserCommand. The desired change is here: obmarg/cynic#1018.