Fix compatibility with newer django-graphene

Bump django from 2.2.4 to 2.2.10

Bumps [django](https://github.com/django/django) from 2.2.4 to 2.2.10.
- [Release notes](https://github.com/django/django/releases)
- [Commits](https://github.com/django/django/compare/2.2.4...2.2.10

)

Signed-off-by: dependabot[bot] <support@github.com>

Newer versions of django-graphene have resolver functions with the
model class as the first argument. Make QueryOptimizer._get_name_from_resolver()
more robust by looking for the first function argument that is either
a string or another partial function.

Bump django from 2.2.2 to 2.2.4

Bumps [django](https://github.com/django/django) from 2.2.2 to 2.2.4.
- [Release notes](https://github.com/django/django/releases)
- [Commits](https://github.com/django/django/compare/2.2.2...2.2.4

)

Signed-off-by: dependabot[bot] <support@github.com>

made name fetching from resolver work for relay connections

Compatibility with graphene-django v2.6.0

Fix variable handling and null values

Dropped support of django 1.9, 1.10 and python 3.4

Add support for object type inputs in prefetch hints