Create naming best practices page

Naming is always the hardest thing but there are some established conventions for naming in the GraphQL community, see:

* https://benjie.dev/graphql/naming
* https://www.apollographql.com/docs/graphos/schema-design/guides/naming-conventions

Other languages also have their own code style/conventions:

* [Rust](https://doc.rust-lang.org/nightly/style-guide/)
* [Kotlin](https://kotlinlang.org/docs/coding-conventions.html)
* [Go](https://go.dev/doc/effective_go)

Feels like having official guidance on graphql.org would be a win for the community.

Start by reviewing the GraphQL naming guidance and the linked conventions for GraphQL, Rust, Kotlin, and Go. Then inspect the graphql.org documentation structure to determine where the page belongs; done means a published naming best practices page with agreed, clearly organized guidance.

Written by the indexing model from the issue text.