Sanity check for GraphQL authorized?

What does this MR do?

Raise an exception if a developer calls any of the GraphQL authorization methods and an authorize :permission is missing from a mutation class.

Previously authorized? would return true in this situation, which although technically is accurate isn't what a developer is expecting!

Does this MR meet the acceptance criteria?

Conformity

• [-] Changelog entry
• [-] Documentation created/updated or follow-up review issue created
• Code review guidelines
• Merge request performance guidelines
• Style guides
• [-] Database guides
• [-] Separation of EE specific content

Performance and testing

• [-] Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• [-] Tested in all supported browsers