GraphQL (resolver) compatibility

[Gozala]

Would love to use this in conjunction with Fanua's graphql support, but running into issues because fauna generates template UDFs from GraphQL schema which then fail migrations because CreateFunction would fail.

While it would be great to have graphql support, even addressing incompatibility going to make a huge difference.

[Gozala]

Not sure how visible that is but it might help if initial schema could be generated from the DB itself.

[Gozala]

Another problem I'm running into with this is that defined resolver functions often refer to indexes and collections defined by graphql which causes script generator to error with message like:

The following resource is not defined anywhere in the resource folders
      type: Index, name: unique_Block_number
  and was referenced from:
      type: Function, name: importBlock
  
  todo: add a boolean to bypass this error in case users
        want to reference resources that were defined manually.

[rts-rob]

Thanks, @Gozala - I'd like to see GraphQL schema support as well!

The other issue you run into is related to #50 - we're currently thinking about the best way to address these all in one update.