fix: Add super calls to GraphqlTrace

[rmosolgo]

Oops -- these trace modules are supposed to call super, where other trace modules may add instrumentation. (Calling &block hands control to GraphQL-Ruby, but skips other trace module code.)

My guess is that these weren't converted to super when this module was migrated off of GraphQL-Ruby's own PlatformTrace module which worked differently (or used to have this same bug?).

Fixes rmosolgo/graphql-ruby#5044

TODO:

• Along the way, I found an issue with how GraphQL::Ruby handles GraphQL::Schema.trace_with(trace_mod) when subclasses already exist and those subclasses have already received .trace_with(...) calls of their own. I'm trying to work that out in Fix default traces added to parent classes after default traces added to child class rmosolgo/graphql-ruby#5045, but that issue is making this test fail (I think...) Never mind, I think I misunderstood because of the ivar reset-related code in the test suite. When I modified my test to use a "fresh" schema class (and manually re-call the setup code), the test failed as expected, then passed when my patch was applied. So I think this is ready to go as-is.

[rmosolgo]

🤔 I force-pushed with with an updated commit message, hoping to pass the "conventional commits validation" test, but it's still failing. Is there a way to make it pass?

[arielvalentin]

@rmosolgo it validates the PR title not the individual commits. I have updated the title.

[rmosolgo]

Oops, thanks!