Integrate web server, GraphQL layer, and data layer

[ra0x3]

• We ideally want to keep GraphQL usage on the web API
  • We're using GraphQL syntax to define our data models (regardless of the outcome of this issue) so it would be nice to stay consistent, and other projects at Fuel use GraphQL
• In order to avoid Remove GraphQL web API #1066, we need to figure out some way to integrate our web server (axum), our GraphQL usage (async-graphql), and our data layer (sqlx)
• The Graph solved for this by just hand-rolling everything
  • https://github.com/graphprotocol/graph-node/blob/master/graphql
• We will most likely have to do the same
• Although we maybe won't be able to use their graph-graphql crate, we could most definitely take inspiration from how they're doing things

Tasks

• Simplify ColumnType usage #1325
• Implement fuel_indexer_graphql_dyn::store::Store for dynamic schema resolution #1310
• Use standard camelCase for GraphQL object fields #931
• Convert PascalCase GraphQL object names into snake_case SQL table names #960
• Add support for u128 and other large integer types in fuel-indexer-graphql #858

[ra0x3]

Steps

• Auto-generate GraphQL schema using contract ABI #846

Will add more steps as we find them

[ra0x3]

@deekerno Just an FYI

• Keep in mind the other two smaller issues in this larger issue ☝🏼
• I closed them out but we should still integrate them into whatever work you do.
• They are:
  • Usage of camelCase field definition names in the schema (e.g., account_id becomes accountId)
  • Using snake_case table names for type definitions that are PascalCased (e.g., indexmetadataentity becomes index_metadata_entity