why use different behavior for the description of query and mutation

* **What is the current behavior?**
Now, the query description only use the `description=...` args for docs, the description or the __doc__ in Typeclass only use for Type docs.
but the mutation use the `description` args or the description of mutation class or the __doc__ of mutation class for both mutation docs and mutation class docs.

* **What is the expected behavior?**
Both query and mutation should share the same logic for docs, first use the `description` arg of the field, then the description of meta class of class, the last is using __doc__ of (the type or mutation) class.

* **Other information** (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow)
dig into code, I find the graphene.mutation has a classmethod func named Field which return graphene.Field with `description=description or cls._meta.description`.

まず、query フィールドの description の処理を、description または cls._meta.description を使って graphene.Field を返す graphene.mutation のクラスメソッド Field と比較します。__doc__ と型または mutation の description が生成されたドキュメントにどのように到達するかを追跡します。query フィールドと mutation フィールドが同じ文書化された優先順位に従い、テストで結果の description が確認できれば完了です。

索引モデルが issue の本文から書いたものです。