Bump graphql-core to 3.2.0

[leszekhanusz]

No description provided.

[codecov-commenter]

Codecov Report

Merging #283 (1de3c31) into master (5440c6c) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master      #283   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           26        26           
  Lines         2060      2060           
=========================================
  Hits          2060      2060           

Impacted Files	Coverage Δ
gql/dsl.py	100.00% <100.00%> (ø)
gql/utilities/build_client_schema.py	100.00% <100.00%> (ø)
gql/utilities/get_introspection_query_ast.py	100.00% <100.00%> (ø)
gql/utilities/parse_result.py	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5440c6c...1de3c31. Read the comment docs.

[leszekhanusz]

@Cito
Should I release the stable 3.0.0 version of gql with graphql-core 3.1.x or should I wait for graphql-core 3.2 stable and merge this PR? What do you think?

[Cito]

If everything is working fine with the 3.2 rc3 version, then I think it's ok - 3,2 final will be released soon and will not have breaking changes.

[Cito]

Sorry, there was a 3.2 rc4 version, and contrary to what I promised above, it contained one breaking change. To make up for this, I have already updated this PR with the necessary fixes. And this should really be the last breaking change before 3.2 final.

[leszekhanusz]

No worries, keep up the good work!

[ddelange]

Does this PR drop support for graphql-core==3.1.*? Or could gql theoretically still allow 3.1.* in install_requires? Doing so would solve dephell ref graphql-python/graphene#1406

Edit: I asked too soon, looks from comments above it is definitely breaking 😅