refactor: clarify the top level graphene query/mutation/subscription

[rexledesma]

Summary

Open source change to accompany https://github.com/dagster-io/internal/pull/507. Felt these names were ungreppable and confusing (are they our implementations, or are they imported from the Graphene library?)

Test Plan

See what breaks, and fix.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/elementl/dagster/6sL5Btk6rsvXPb7icNCDcc7qijP4
✅ Preview: Canceled

[Deployment for 7abd0ce canceled]

[rexledesma]

Current dependencies on/for this PR:

• master
  • PR refactor: clarify the top level graphene query/mutation/subscription #5782 (this PR)

This comment was auto-generated by Graphite and will continue to be automatically updated while this PR remains open.

[gibsondan]

fully support renaming the python class name - renaming the Graphql type name will require some changes on the JS side (grep for "Query" or "Mutation", some tests use it and check the typename) - I don't think it will be a user-facing breaking change though unless they have some strange queries?

Updated code

[rexledesma]

Updated https://github.com/dagster-io/internal/pull/507 as the corresponding change to unbreak internal

[hellendag]

You may also need to change the Query: in AppCache, but I'm actually thinking maybe we don't need that typePolicies anymore anyway...

[gibsondan]

internal builds are failing but i assume there's a separate PR for that