Eager load the GraphQL schema in specs
What does this MR do?
Avoid counting on Rails eager loading the GraphQL types, but preload them before the specs.
This would avoid loading the schema in 2 separate threads concurrently (1 inside the specs, 1 inside the test-server that will receive requests). Loading the schema in parallel like that could cause duplicate definition errors.
Inspired by https://github.com/rmosolgo/graphql-ruby/issues/1505#issuecomment-408209171
I wonder if this particular thing would end up being an issue in production when we switch to a multi-threaded environment