refactor graphql objects to use class based approach

[Tooyosi]

refactor graphql objects to use class based approach and remove restriction on gem

GraphQL::ObjectType.define will be removed in GraphQL-Ruby 2.0; use a class-based definition instead. See https://graphql-ruby.org/schema/class_based_api.html. -> called from /app/app/models/workflow.rb:4:in class:Workflow'
GraphQL::Schema.define will be removed in GraphQL-Ruby 2.0; use a class-based definition instead. See https://graphql-ruby.org/schema/class_based_api.html.
-> called from /app/app/graphql/caesar_schema.rb:1:in <main>' GraphQL::ObjectType.define will be removed in GraphQL-Ruby 2.0; use a class-based definition instead. See https://graphql-ruby.org/schema/class_based_api.html. -> called from /app/app/graphql/query_root.rb:1:in

'
GraphQL::ObjectType.define will be removed in GraphQL-Ruby 2.0; use a class-based definition instead. See https://graphql-ruby.org/schema/class_based_api.html.
-> called from /app/app/graphql/mutation_root.rb:1:in <main>' GraphQL::ObjectType.define will be removed in GraphQL-Ruby 2.0; use a class-based definition instead. See https://graphql-ruby.org/schema/class_based_api.html. -> called from /app/app/models/credential.rb:2:in class:Credential'
GraphQL::ScalarType.define will be removed in GraphQL-Ruby 2.0; use a class-based definition instead. See https://graphql-ruby.org/schema/class_based_api.html.
-> called from /app/app/graphql/types/time_type.rb:1:in <main>' GraphQL::ObjectType.define will be removed in GraphQL-Ruby 2.0; use a class-based definition instead. See https://graphql-ruby.org/schema/class_based_api.html. -> called from /app/app/models/extract.rb:2:in class:Extract'
GraphQL::ObjectType.define will be removed in GraphQL-Ruby 2.0; use a class-based definition instead. See https://graphql-ruby.org/schema/class_based_api.html.
-> called from /app/app/models/subject_reduction.rb:4:in <class:SubjectReduction>' GraphQL::ObjectType.define will be removed in GraphQL-Ruby 2.0; use a class-based definition instead. See https://graphql-ruby.org/schema/class_based_api.html. -> called from /app/app/models/subject_action.rb:2:in class:SubjectAction'
GraphQL::ObjectType.define will be removed in GraphQL-Ruby 2.0; use a class-based definition instead. See https://graphql-ruby.org/schema/class_based_api.html.
-> called from /app/app/models/user_reduction.rb:4:in <class:UserReduction>' GraphQL::ObjectType.define will be removed in GraphQL-Ruby 2.0; use a class-based definition instead. See https://graphql-ruby.org/schema/class_based_api.html. -> called from /app/app/models/user_action.rb:2:in class:UserAction'
GraphQL::EnumType.define will be removed in GraphQL-Ruby 2.0; use a class-based definition instead. See https://graphql-ruby.org/schema/class_based_api.html.
-> called from /app/app/models/data_request.rb:3:in <class:DataRequest>' GraphQL::EnumType.define will be removed in GraphQL-Ruby 2.0; use a class-based definition instead. See https://graphql-ruby.org/schema/class_based_api.html. -> called from /app/app/models/data_request.rb:13:in class:DataRequest'
GraphQL::ObjectType.define will be removed in GraphQL-Ruby 2.0; use a class-based definition instead. See https://graphql-ruby.org/schema/class_based_api.html.
-> called from /app/app/models/data_request.rb:26:in <class:DataRequest>' GraphQL::ScalarType.define will be removed in GraphQL-Ruby 2.0; use a class-based definition instead. See https://graphql-ruby.org/schema/class_based_api.html. -> called from /app/app/graphql/types/json_type.rb:3:in '
GraphQL::EnumType.define will be removed in GraphQL-Ruby 2.0; use a class-based definition instead. See https://graphql-ruby.org/schema/class_based_api.html.
-> called from /app/app/graphql/types/action_status_type.rb:1:in <main>'

Resolving console warnings in caesar.

See here
And here

[yuenmichelle1]

Looks good as far as I can tell. Testing locally it looks good. I didnt really test any mutation (other than the check to see if they can still be called), but I don't think anyone was really using those.