[naming-convention] Add Query-specific option

I think there could be a new option that targets the queries because the naming convention could be different from a field definition on a normal type.

For example, I may want to forbid the queries to have get prefixes because queries are always “GET” but still allows other object type definitions, then I can add the following rule to eslint config:

"@graphql-eslint/naming-convention": [
  "error",
  {
    "QueryFieldDefinition": { "format": "camelCase", "forbiddenPrefixes": ["get"] },
    "FieldDefinition": { "format": "camelCase" },
  }
]

type Query {
  getUser: User # Error
  user: User # OK
}

type User {
  getter: User # OK
}

If it makes sense I can try creating a PR for this 😃

[dotansimha]

Available in @graphql-eslint/eslint-plugin@0.8.0

[eddeee888]

@dotansimha I have created a PR for this: https://github.com/dotansimha/graphql-eslint/pull/256 Please have a look when you have a chance, thanks! 🙏