Better key management for GQL API keys

[mastercactapus]

What problem would you like to solve? Please describe:
Currently managing GQL API keys is very manual and tedious, and it's missing some features that could really help.

Describe the solution you'd like:

• Token rotation implemented similarly to universal integration keys, expiration tied to token
• Versioned keys, instead of duplicate & rename, allow versioning keys and maybe a diff function to compare the queries; making it more organized and easier to iterate
• An "open in explorer" button to open a key's query in the GraphQL API explorer
• A way for users to either create their own keys (tied to a specific service/schedule, etc...) or a way for them to request through-app from an Admin. Currently the process is out-of-band, give admin query, admin creates and has to securely transfer the token to the user.
• Maybe necessary for above, but the ability to write an Expr expression to inspect/validate/restrict variables. This would allow making a key that is locked to specific schedules, or that can only create services with a prefixed name.

Describe alternatives you've considered:
The current solution is workable but very time consuming.