Disallow naming types as reserved words

[tolkienosborn]

Summary

We recently had out entire graphQL failover on an instance in Heartcore and it was due to using the reserved word "element" as an element type. Can you implement a non-allow or warning based system to stop the reserved word list from being used when naming elements and properties in Heartcore

https://docs.umbraco.com/umbraco-heartcore/api-documentation/graphql/schema-generation#reserved-type-names-and-property-aliases

Use case

To stop potential downtime and drain on support tickets to fix

[github-actions[bot]]

Hi there @tolkienosborn!

Firstly, a big thank you for your suggestion. Every piece of feedback we receive helps us to make Heartcore better.

We really appreciate your patience while we wait for our team to have a look at this. We'll assess whether your suggestion is something we can action and let you know roughly what you can expect next.

We wish we could work with everyone directly and assess your suggestion immediately but we're in the fortunate position of having lots of feedback to work with and only a few humans who are able to do anything with it. We are making progress though, and we'll keep you posted when we have something to report!

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂